Quoting Andreas Gruenbacher <agruen@xxxxxxx> > On Sunday 17 January 2010 03:22:10 am Junio C Hamano wrote: >> Tests? > > Sure if you think it's worth a regression test ... Of course you must have a test when you are fixing things. Tests aren't to prove that your patch is correct. They are to prevent other people from breaking your change long after you leave the project. > Sure if you think it's worth a regression test ... "git apply -p2" of the > following patch fails... You do so by sending a patch to add your new test in t/; adding to an existing related test is preferred if the test is small. Junio, in case you don't want to wait for Andreas, you can squash this test in. diff --git a/t/t4120-apply-popt.sh b/t/t4120-apply-popt.sh index 83d4ba6..b463b4f 100755 --- a/t/t4120-apply-popt.sh +++ b/t/t4120-apply-popt.sh @@ -22,4 +22,9 @@ test_expect_success 'apply git diff with -p2' ' git apply -p2 patch.file ' +test_expect_success 'apply with too large -p' ' + test_must_fail git apply --stat -p3 patch.file 2>err && + grep "removing 3 leading" err +' + test_done -- Nanako Shiraishi http://ivory.ap.teacup.com/nanako3/ -- 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