checkout: do not check out unmerged higher stages randomly
authorJunio C Hamano <gitster@pobox.com>
Fri, 29 Aug 2008 20:40:36 +0000 (13:40 -0700)
committerJunio C Hamano <gitster@pobox.com>
Sat, 30 Aug 2008 23:46:25 +0000 (16:46 -0700)
During a conflicted merge when you have unmerged stages for a
path F in the index, if you said:

$ git checkout F

we rewrote F as many times as we have stages for it, and the
last one (typically "theirs") was left in the work tree, without
resolving the conflict.

This fixes it by noticing that a specified pathspec pattern
matches an unmerged path, and by erroring out.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
No differences found