From: Junio C Hamano <gitster@pobox.com>
Date: Mon, 21 Jan 2013 19:01:19 GMT
Subject: Re: [RFC] git rm -u
Message-ID: <7v1udegy2o.fsf@alter.siamese.dyndns.org>
In-Reply-To: <7v622qhouc.fsf@alter.siamese.dyndns.org>

Junio C Hamano <gitster@pobox.com> writes:

> Piotr Krukowiecki <piotr.krukowiecki@gmail.com> writes:
>
>> Do you mean "git add" will be disallowed without "." or ":/" argument?
>> Or will this change in future and "git add" without argument will me
>> "whole tree", same as ":/" ?
>
> No.  This is only about "git add -u<RETURN>", not any other forms of
> "git add ...with or without other args...".

This part is still correct, but all the remainder of the message I
am responding to is a total garbage, written from faulty memory
without fact check.  Sorry about noise.

> "git add -u<RETURN>" historically meant,...

The very original "git add -u<RETURN>" done at v1.5.2-rc0~17^2
(git-add -u: match the index with working tree., 2007-04-20) did
update the index with every change under the root of the working
tree, no matter where you were.

But v1.5.2.5~1 (git-add -u paths... now works from subdirectory,
2007-08-16) changed the semantics to limit the operation to the
working tree.  The log message seems to suggest that this was a
deliberate semantics change post release (i.e. the "tree-wide" was a
bug); I do not recall if there was a discussion and concensus when
this change was made, though.