Re: non-empty index with git commit -a

On Wed, Feb 16, 2011 at 03:41:35PM +0100, Michael J Gruber wrote:

quoted

If you want to have an option that specifically prevents the "git commit
-a" muscle memory thing, then go for it. I'm guessing it is the most
common "oops" one. Even with an index reflog, you might want it on top.

But it just seems silly to me to not protect at the same time against
the other ways you can lose state from the index.

so that keeping one backup would be enough? I.e. an automated way of
doing "cp index index.bak" before an index update and some "reset"
incarnation to revive the copy?

No, I am not proposing one backup. I am proposing a reflog with multiple
entries that would be expired on the regular reflog schedule.

-Peff