On Thu, Feb 14, 2008 at 11:54:32AM -0500, Jeff King wrote: > 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 Actually, this only finds the problem in the current 'next', where git-status barfs with an error, and not in the first commit that exhibits the problem, where only the results are incorrect. I tried making a "git commit" test, but it seems that the commit actually happens correctly (although if you do not specify -m, it does a run_status, and ends up barfing). So the problem really is that the index is screwed up after we decide what to commit but before we do the status. -Peff - 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
