Re: My use case

From: Ron Garret <ron1@flownet.com>
Date: Jan 30, 2010, 18:29 UTC
Message-ID: <ron1-A58BC7.10295430012010@news.gmane.org>
In-Reply-To: <20100130174844.GD788@thunk.org>

In article <20100130174844.GD788@thunk.org>, tytso@mit.edu wrote:

Show 13 quoted lines

> On Sat, Jan 30, 2010 at 12:54:13AM -0800, Ron Garret wrote:
> > Don't forget, I'm integrating this *into* the IDE, not just using it 
> > *for* the IDE.  So I want to just have a context menu on each code 
> > window with "SNAPSHOT" and "ROLLBACK" items that Just Work.  The casual 
> > user won't even know that there's git behind the scenes.
> 
> This is a workflow question, I suppose, but I find things work much
> better if you can get the user to give you explicit commit boundaries
> so that (a) bisect works, and (b) they can describe what each commit
> does, and (c) so they can more easily move specific bug fixes or
> features between different release branches.  The free-form hacking
> more may be nice, and very "LISP-like", but there are some real
> advantages to having explicitly describable and documented commits.

You are absolutely right. That is another reason why having the individual files tracked separately from the main project would be a good thing if I can get it to work. (It would be kind of like having a git-stash on a per-file basis.)

rg