From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date: Sun, 27 Feb 2011 16:52:34 GMT
Subject: Re: [PATCH 1.8.0] add: make "add -u" update full tree without pathspec
Message-ID: <AANLkTi=BwTHRWcUu26VLWAhFupmuJpu8fvOF98--HJ5f@mail.gmail.com>
In-Reply-To: <7vei6t4uwa.fsf@alter.siamese.dyndns.org>

On Sun, Feb 27, 2011 at 5:46 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Perhaps in this order:
>
> Step 1, as soon as possible:
>
>  * Introduce "add.make_update_global" configuration variable, and toggle
>   the above variable when it is explicitly given; also record the fact
>   that you actually saw this variable in the config parser regardless of
>   the value that is given;

Ermm.. compat.make_update_global, with the intent that the config will
be dropped in future (1.9.0 maybe)?

>  * Document the configuration variable as a new feature, without
>   indicating that that will be the new default in the future, but
>   strongly recommending that existing scripts should be updated and new
>   scripts should be written the variable in mind---namely, their use of
>   "add -u" should use "." if they are relying on the current "limit to
>   cwd" behaviour.

There's a problem. I use git on many machines. Some will have this
config enabled, some will not (yet). Perhaps a third option, which
will print something when "git add -u" is issued as a reminder? I
don't know. What I need is to notice old behavior of "git add -u"
before it's too late.

> Step 4, 3 cycles after 1.8.0:
>
>  * Drop the warning.

Step 5 (1.9.0 or later):

 * Drop compat.make_update_global.
-- 
Duy