Ralf Thielow <ralf.thielow@xxxxxxxxx> writes: > diff --git a/t/t5709-clone-refspec.sh b/t/t5709-clone-refspec.sh > new file mode 100755 > index 0000000..69a0779 > --- /dev/null > +++ b/t/t5709-clone-refspec.sh > @@ -0,0 +1,155 @@ > +#!/bin/sh > + > +test_description='test refspec written by clone-command' > +. ./test-lib.sh > + > +test_expect_success 'setup' ' > + # Make two branches, "master" and "side" > + ... > + # explicit --single with tag > + git clone --single-branch --branch two . dir_tag && > + > + # advance both "master" and "side" branches > + git checkout side && > + echo five >file && > + git commit -a -m five && > + git checkout master && > + echo six >file && > + git commit -a -m six > +' > + > + ... > +test_expect_success '--single-branch with explicit --branch with tag fetches updated tag' ' > + git tag -d two && git tag two && Curious. Was it insufficient to update this tag at the end of the "setup" process like everybody else where # advance both "master" and "side" branches happens? Not that it is wrong to do this, but it looked somewhat inconsistent. -- 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