Re: Change in "git checkout" behaviour between 1.6.0.2 and 1.6.0.3

Michael J Gruber [off-list ref] writes:

[...]

Bisecting gives:


5521883490e85f4d973141972cf16f89a79f1979 is first bad commit
commit 5521883490e85f4d973141972cf16f89a79f1979
Author: Junio C Hamano [off-list ref]
Date:   Sun Sep 7 19:49:25 2008 -0700

    checkout: do not lose staged removal

I got the same, which is reassuring.

Looks like a deliberate change with (what seems to me to be) an
unfortunate interaction with "git clone -n"