Re: "git add -u" broken in git 1.7.4?
- From
Jeff King <peff@peff.net>
- Date
- Feb 7, 2011, 05:53 UTC
- Message-ID
- <20110207055314.GA5511@sigill.intra.peff.net>
- In-Reply-To
- <7vwrlcv1ea.fsf@alter.siamese.dyndns.org>
On Sun, Feb 06, 2011 at 09:50:37PM -0800, Junio C Hamano wrote:
Show 16 quoted lines
> Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes: > > > Sebastian Pipping <webmaster@hartwork.org> writes: > > > >> I was and I can confirm the different behaviour with 1.7.4 over here: it > >> does work on the root directory of the repo as you supposed. > > > > What do you mean by "it does not work"? > > > > "git add -u" adds files under the current directory, and it always > > did. > > As it takes pathspecs (think "git add -u this-file"), it fundamentally > shouldn't be tree-wide. I think the original implementation didn't take > pathspecs and was mistakenly done as tree-wide operation, but I think it > was fixed rather quickly.
Is "git add -p" broken, then? It takes pathspecs relative to the current directory, but "git add -p" without arguments operates from the root, not from the current subdirectory.
-Peff