@matheusbsbs / matheus-bagliano / commits / 4170af8232
Fork 0

checkout -f: do not leave untracked working tree files.

Earlier we did not consider untracked working tree files "precious", but we have always considered them fair game to clobber. These days, branch switching by read-tree is more careful and tries to protect untracked working tree files. This caused the following workflow to stop working: git checkout one-branch-with-file-F git checkout -f another-without-file-F git pull . one-branch-with-file-F Because the second checkout leaves F from the previous state as untracked file in the working tree, the merge would fail, trying to protect F from being clobbered. This changes "git checkout -f" to remove working tree files that are known to git in the switched-from state but do not exist in the switched-to state, borrowing the same logic from "reset --hard". Signed-off-by: Junio C Hamano <junkio@cox.net>

Junio C Hamano committed Jun 20, 2006 at 02:47 UTC 4170af82328e50a75723cee084ae779e7a882b9d
1 file changed +1 -2
git-checkout.sh
+1 -2
@@ -137,8 +137,7 @@ fi
137
138 if [ "$force" ]
139 then
140 - git-read-tree --reset $new &&
141 - git-checkout-index -q -f -u -a
140 + git-read-tree --reset -u $new
141 else
142 git-update-index --refresh >/dev/null
143 merge_error=$(git-read-tree -m -u $old $new 2>&1) || (