From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date: Wed, 16 Feb 2011 08:29:19 GMT
Subject: Re: non-empty index with git commit -a
Message-ID: <AANLkTikmxHQpir5YbiBihASL1SYf_AyoUHKT3nqKS-iP@mail.gmail.com>
In-Reply-To: <AANLkTinbcHW+ja7T=PiCEorNdnK6W2DvA_c9F8JTEMKB@mail.gmail.com>

On Wed, Feb 16, 2011 at 3:18 PM, Sverre Rabbelier <srabbelier@gmail.com> wrote:
> Heya,
>
> On Wed, Feb 16, 2011 at 03:20, Jonathan Nieder <jrnieder@gmail.com> wrote:
>> If I remember the discussion[1] correctly, by requiring a separate
>> add -u step (or commit -f -a) if the "I don't trust my fingers"
>> configuration is enabled.
>
> That would definitely work for me. The question then is, should git
> consider the index precious by default, or not? That is, should that
> value default to true in 1.8?

Is it insane that "git commit -a" still commits everything, but then

1. If old index is different from old HEAD, keeps index as is and warn users
2. If old index is the same as old HEAD, update index with new HEAD

?
-- 
Duy