Re: What's cooking in git.git (Feb 2013, #05; Tue, 12)

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 22, 2013, 16:58 UTC
Message-ID: <7vip5ks2sy.fsf@alter.siamese.dyndns.org>
In-Reply-To: <87hal4n3z1.fsf@catnip.gol.com>

Miles Bader <miles@gnu.org> writes:

Show 7 quoted lines

> Junio C Hamano <gitster@pobox.com> writes:
>>  * Introduce "git add --ignore-removal" option in the release after
>>    the current cycle (a new feature is too late for this cycle):
>
> Too late in the cycle even if the option is simply ignored ... ?
>
> [To extend the range of git versions where it's not an error]

I'd feel safer to have enough time to cook the "alleged no-op" before merging it to 'master' and include it in a release.

Possible implementation mistakes aside, "--ignore-removal" is probably too long to type, we haven't even discussed if it deserves a short-and-sweet single letter option, the obvious "-i" is not available, etc. etc. I do not think we have a concensus that the transition plan outlined is a good way to go in the first place.

So, I do think it is a bit too late for this cycle, especially when we still have doubts about the design. Actually it is *I* who have doubts; I do not even know if other people share the doubts or they support the direction wholeheartedly.