Re: [PATCH 1/2] require pathspec for "git add -u/-A"
- From
Jeff King <peff@peff.net>
- Date
- Mar 12, 2013, 11:28 UTC
- Message-ID
- <20130312112840.GA13186@sigill.intra.peff.net>
- In-Reply-To
- <vpqmwubgsqy.fsf@grenoble-inp.fr>
On Sun, Mar 10, 2013 at 04:49:09PM +0100, Matthieu Moy wrote:
Show 14 quoted lines
> Junio C Hamano <gitster@pobox.com> writes: > > > As promised in 0fa2eb530fb7 (add: warn when -u or -A is used without > > pathspec, 2013-01-28), "git add -u/-A" that is run without pathspec > > in a subdirectory will stop working sometime before Git 2.0, to wean > > users off of the old default, in preparation for adopting the new > > default in Git 2.0. > > I originally thought this step was necessary, but I changed my mind. The > warning is big enough and doesn't need to be turned into an error. > > If this step is applied, it should be applied at 2.0, not before, as > this is the big incompatible change. Re-introducing a new behavior won't > harm users OTOH.
FWIW, I agree with this. The warning is enough without an error period (unless the intent was to switch to the error and stay there forever, but I do not think that is the proposal).
-Peff
PS I wonder how others are finding the warning? I'm finding it slightly annoying. Perhaps I just haven't retrained my fingers yet. But one problem with that retraining is that I type "git add -u" from the root _most_ of the time, and it just works. But occasionally, I get the "hey, do not do that" warning, because I'm in a subdir, even though I would be happy to have the full-tree behavior. I guess we already rejected the idea of being able to shut off the warning and just get the new behavior, in favor of having people specify it manually each time?