On Sun, Feb 27, 2011 at 5:46 PM, Junio C Hamano <gitster@xxxxxxxxx> 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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html