Re: What's cooking in git.git (Apr 2013, #05; Mon, 15)

From: Junio C Hamano <gitster@pobox.com>
Date: Apr 17, 2013, 17:08 UTC
Message-ID: <7vk3o1f5kb.fsf@alter.siamese.dyndns.org>
In-Reply-To: <87wqs1xi9h.fsf@hexa.v.cablecom.net>

Thomas Rast <trast@inf.ethz.ch> writes:

> I can see that problem, but along the same lines, why shouldn't I have
> an expectation that when I say 'git add "*.py"' it removes stuff that I
> have removed?

You _should_ have that expectation.

If it does not remove with the code that has been prepared for 2.0 (that is a bit beyond 'next'), then it is a big problem, but I think it does remove the removed python source without "-A", as long as you give a pathspec "*.py" (with quotes around it) that match it.

I think it is just the warning code avoiding extra complexity and overhead, if you are talking about not getting warning in the pre-2.0 step that is in 'next'. Patches are very much welcomed, especially the ones that come before I get around to it ;-)