On Thu, Feb 14, 2008 at 04:51:04PM +0000, Johannes Schindelin wrote: > I experienced the same bug, but when I looked in the tests, I had the > impression that it tested for that very bug, and succeeded. And I did not > have time to look into it further. Which test did you think was checking for it? > Speaking of tests... How about it? I included a "from scratch" test case in my last message which I think helps in understanding what's happening. But if we just want to test this condition (it fails because there is a new file that is added but not committed): diff --git a/t/t7502-status.sh b/t/t7502-status.sh index b64ce30..11e5655 100755 --- a/t/t7502-status.sh +++ b/t/t7502-status.sh @@ -128,4 +128,8 @@ test_expect_success 'status without relative paths' ' ' +test_expect_success 'status of partial commit excluding new file in index' ' + git status modified +' + test_done - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
