Re: non-empty index with git commit -a
- From
Jeff King <peff@peff.net>
- Date
- Feb 16, 2011, 09:54 UTC
- Message-ID
- <20110216095415.GA12578@sigill.intra.peff.net>
- In-Reply-To
- <AANLkTik_F=d1CjNVfj35wgv0pL1LefOMnttXjs=s2wCQ@mail.gmail.com>
On Wed, Feb 16, 2011 at 09:52:23AM +0000, Sverre Rabbelier wrote:
Show 6 quoted lines
> On Wed, Feb 16, 2011 at 08:51, Jeff King <peff@peff.net> wrote: > > I can just as easily run "git add -u", or "git add -p" on top of some > > changes and then realize afterwards that I actually wanted the previous > > index state. > > I disagree, those are all index manipulation tools, `git commit -a` is not.
So? Your question was whether index state is precious. If it's precious, shouldn't we be keeping a history of it?
-Peff