From: Piotr Krukowiecki Date: Mon, 21 Jan 2013 08:09:42 GMT Subject: Re: [RFC] git rm -u Message-ID: In-Reply-To: <7v1udfn0tm.fsf@alter.siamese.dyndns.org> On Sun, Jan 20, 2013 at 7:53 PM, Junio C Hamano wrote: > Matthieu Moy writes: > >> Implementing "git rm -u" as a tree-wide command would create a >> discrepancy with "git add -u". Implementing it as a "current directory" >> command would make the migration harder if we eventually try to change >> "git add -u". Perhaps "git rm -u" should be forbidden from a >> subdirectory (with an error message pointing to "git rm -u :/" and "git >> rm -u ."), waiting for a possible "git add -u" change. > > Yeah, that sounds sensible. Start with a "'git rm -u' is forbidden > without arguments", give advise to use either "." or ":/". And stop > there. > > The first step of "git add -u" migration plan would be to warn when > no argument is given and update all the existing index entries, and > give the same advise to use either "." or ":/". Keep this for three > cycles: 3 * (8 to 10 weeks per cycle) = 27 weeks ~ 1/2 year. > > The second step would be to forbid "git add -u", and keep the > advise. That will make it in-line with "git rm -u". 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 ":/" ? -- Piotr Krukowiecki