On Wed, Mar 13, 2013 at 10:44:25AM -0700, Junio C Hamano wrote: > > +# Note that this is scheduled to change in Git 2.0, when > > +# "git add -u" will become full-tree by default. > > +test_expect_success 'update did not touch files at root' ' > > + cat >expect <<-\EOF && > > + check > > + top > > + EOF > > + git diff-files --name-only >actual && > > + test_cmp expect actual > > +' > > The last "git add -u" we have beforet his block is this test piece: > > test_expect_success 'update from a subdirectory' ' > ( > cd dir1 && > echo more >sub2 && > git add -u sub2 > ) > ' > > That is not "git add -u" without pathspec, which is the only thing > we are transitioning at Git 2.0 boundary. Oops, you're right. I just saw the "cd" and totally missed the pathspec. The correct test should be: -- >8 -- Subject: [PATCH] t2200: check that "add -u" limits itself to subdirectory This behavior is due to change in the future, but let's test it anyway. That helps make sure we do not accidentally switch the behavior too soon while we are working in the area, and it means that we can easily verify the change when we do make it. Signed-off-by: Jeff King <peff@xxxxxxxx> --- t/t2200-add-update.sh | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/t/t2200-add-update.sh b/t/t2200-add-update.sh index 4cdebda..c317254 100755 --- a/t/t2200-add-update.sh +++ b/t/t2200-add-update.sh @@ -80,6 +80,22 @@ test_expect_success 'change gets noticed' ' ' +# Note that this is scheduled to change in Git 2.0, when +# "git add -u" will become full-tree by default. +test_expect_success 'non-limited update in subdir leaves root alone' ' + ( + cd dir1 && + echo even more >>sub2 && + git add -u + ) && + cat >expect <<-\EOF && + check + top + EOF + git diff-files --name-only >actual && + test_cmp expect actual +' + test_expect_success SYMLINKS 'replace a file with a symlink' ' rm foo && -- 1.8.2.rc2.7.gef06216 -- 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