Miles Bader <> writes:

> Junio C Hamano <> 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.

To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to
More majordomo info at

Reply via email to