Re: non-empty index with git commit -a

On Wed, Feb 16, 2011 at 09:52:23AM +0000, Sverre Rabbelier wrote:

On Wed, Feb 16, 2011 at 08:51, Jeff King [off-list ref] wrote:

quoted

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