Jeff King [off-list ref] writes:
I probably shouldn't have included this middle patch at all, because
the interesting thing is what happens when we do turn it off.
Actually, I think the warning is the most important part. With the
warning enabled, people should notice they are doing something
potentially wrong and dangerous, so the warning essentially fixes the
issue in the short term.
I also think that changing the default behavior later makes sense (but I
agree that replacing "in Git 2.0" with "in a future version of Git" is
better, there's no urgency for this change and people start looking
forward 2.0).
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/