From: Nguyen Thai Ngoc Duy Date: Mon, 07 Feb 2011 07:29:23 GMT Subject: Re: "git add -u" broken in git 1.7.4? Message-ID: In-Reply-To: <7vhbcguytf.fsf@alter.siamese.dyndns.org> On Mon, Feb 7, 2011 at 1:46 PM, Junio C Hamano wrote: > I actually do not mind too much myself if all commands that can take > pathspecs consistently defaulted to "full-tree" pathspec given no > pathspec.  But if we were to go that route, everybody should join their > voice to defend that decision when outside people say "in 1.8.0 'git grep' > run from a subdirectory shows matches from all the irrelevant parts of the > tree; with all the cruft its output is unreadable". I won't be the sole > champion of such a behaviour when I do not fully believe in it. That could be one more item for the next git survey (i.e. how do you want the defaults to be?). Most of people in this list more or less breath git already and therefore are bias (I think). Personally "git add -u --full-tree" is good enough to me. It does have the same problem that git --full-tree has: what *.h in "git grep --full-tree -- '*.h'" means. But I'm OK with not supporting that case until we agree on something. -- Duy