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

> > 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 ;-)
> 
> I took a brief look at the code, and as you said "add" needs to know
> about submodules, and the best fix looks to me to take the same
> approach Jonathan came up with to de-noise the "add -u/-A" topic.
> 
> That is, to scan the working tree to actually see if we would record
> removals to the index in 2.0, but not remove them in this current
> version, and give the warning when the differences in the behaviours
> matter.