Jonathon Mah <me@xxxxxxxxxxxxxxx> writes: > +test_expect_success 'prune: handle alternate object database' ' > + test_create_repo A && > + (cd A && > + echo "Hello World" >file1 && > + git add file1 && > + git commit -m "Initial commit" file1) && > + git clone -s A B && > + (cd B && > + echo "foo bar" >file2 && > + git add file2 && > + git commit -m "next commit" file2 && > + git prune) > +' The issue does not have much to do with introducing new path to the cloned repository, or the original having any specific content for that matter, so I am tempted to simplify the above to something like this intead: test_create_repo A && git -C A commit --allow-empty -m "initial commit" && git clone --shared A B && git -C B commit --allow-empty -m "next commit" && git -C B prune Thanks. -- 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