Re: [RFC] best way to show diff of commit

From: Pierre Habouzit <madcoder@debian.org>
Date: Nov 25, 2007, 22:09 UTC
Message-ID: <20071125220902.GB21121@artemis.corp>
In-Reply-To: <20071125212748.GB23820@fieldses.org>

On Sun, Nov 25, 2007 at 09:27:48PM +0000, J. Bruce Fields wrote:

Show 17 quoted lines

> On Sun, Nov 25, 2007 at 10:18:31PM +0100, Pierre Habouzit wrote:
> >   There is specific script I run in my vim with git, that tries to show
> > from the 'status' git commit shows in the buffer which list of files has
> > changed, and builds a diff from it quite clumsily[0].
> > 
> >   I wonder how hard it would be for git commit to "stash" the current
> > commit being sent somewhere editors would be able to have a look at (an
> > alternate index is probably fine). Note that maybe I'm stupid and
> > overlooked that such a thing already exists.  I'd like to have it in two
> > flavors: normal and amend mode. normal mode would show what the
> > resulting commit diff looks like, and the amend mode only shows the
> > incrementall diff the amend adds to the previous commit.
> > 
> >   My question is: what do you think is the best way to do that, and
> > where ?
> 
> Have you checked whether "git-commit -v" already does what you want?

  Hmm it doesn't because I would have to call git commit -v each time I
commit and well I _like_ having the status better. And moreover I want
the diff to go in a separated buffer too.

  I'd rather have some kind of way to have git-commit let a trail of
what he's doing if the user validate the commit, and use that from the
editor. I'm sure it would be useful to simple GUIs as well (most
advanced GUIs would like to have fine control to what gets commited and
are likely to have the command like used quite right).

-- 
·O·  Pierre Habouzit
··O                                                madcoder@debian.org
OOO                                                http://www.madism.org