"Aneesh Kumar" <aneesh.kumar@xxxxxxxxx> writes: > I am still having failure with the top of the tree. I guess it is > because git rm exit with status 0. Please don't guess, but validate (I know you are capable of doing so). What I would do to see what is happening would be to do something like the attached patch and re-run the test. BTW, you did "sh -x t3600-rm.sh" which is very good. I usually do it when debugging hard-to-debug testsuite problem, especially ones which I do not know intimately, written by somebody else, like this: sh -x tXXXX-that-test.sh -i The -i option makes it immediately stop at the first test failure. -- >8 -- diff --git a/git-rm.sh b/git-rm.sh index fda4541..622ffca 100755 --- a/git-rm.sh +++ b/git-rm.sh @@ -43,6 +43,8 @@ case "$#" in ;; esac +set -x + if test -f "$GIT_DIR/info/exclude" then git-ls-files -z \ - : 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