From: Carl Baldwin Date: Thu, 02 Feb 2006 16:30:12 GMT Subject: Re: Two ideas for improving git's user interface Message-ID: <20060202163012.GB10937@hpsvcnb.fc.hp.com> In-Reply-To: <87lkwupsbr.wl%cworth@cworth.org> On Wed, Feb 01, 2006 at 03:33:44PM -0800, Carl Worth wrote: > Is it ever useful (reasonable, desirable) to commit file > contents that differ from the contents of the working > directory? What _is_ useful about the status quo is the ability to make some minor change, update that change to the index when I've decided that it is a good change and then use git diff to see what I've incrementally changed in the same file since that update. That way new incremental changes can be viewed independantly of the change I've already decided was good. > What I would love to have is the ability to pass the same arguments to > git diff to get a preview of what any get commit would do. For > example, something like: > > git diff # would be a preview of: > git commit 'git diff --cached' does this. > git diff -a # would be a preview of: > git commit -a 'git diff HEAD' does this. > git diff fileA fileB # would be a preview of: > git commit fileA fileB Paths can be specified in conjunction with the above commands. Yes, these are idioms specific to git and are not immediately intuitive to the new user. However, if the user has access to a good tutorial that walks through these scenerios its not so bad. Carl -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Carl Baldwin RADCAD (R&D CAD) Hewlett Packard Company MS 88 work: 970 898-1523 3404 E. Harmony Rd. work: Carl.N.Baldwin@hp.com Fort Collins, CO 80525 home: Carl@ecBaldwin.net - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -