Francis Moreau venit, vidit, dixit 01/12/09 10:17: > Hello, > > Junio C Hamano <gitster@xxxxxxxxx> writes: > >> Don't use explicit --tags blindly. It says "no matter what kind of tag, >> transfer everything under refs/tags". Otherwise you won't see a >> difference. > > Well: > > $ git --version > git version 1.6.0.4 > $ mkdir test-tag > $ cd test-tag/ > $ date > A > $ git init > Initialized empty Git repository in > /home/fmoreau/tmp/git/test-tag/.git/ > $ git add . > $ git commit -a -s -m "Init" > Created initial commit be8750e: Init > 1 files changed, 1 insertions(+), 0 deletions(-) > create mode 100644 A > $ cd .. > $ git clone --bare test-tag test-tag.git > Initialized empty Git repository in /home/fmoreau/tmp/git/test-tag.git/ > $ cd test-tag > $ git tag light > > $ git tag -a -m "Annoted tag" annoted > $ git push ../test-tag.git > Everything up-to-date > $ git push --tags ../test-tag.git > Counting objects: 1, done. > Writing objects: 100% (1/1), 166 bytes, done. > Total 1 (delta 0), reused 0 (delta 0) > Unpacking objects: 100% (1/1), done. > To ../test-tag.git > * [new tag] annoted -> annoted > * [new tag] light -> light > > It looks like they're no difference for git-push... > > That said the documentation about this is rather cryptic IMHO: > > ,----[ man git-push ] > | --tags > | All refs under $GIT_DIR/refs/tags are pushed, in > | addition to refspecs explicitly listed on the command > | line. > `---- > > From a user point of view, the word lightweight is missing here. Why > not simply saying: > > ,---- > | All kind of tags are pushed with this option _otherwise_ only annoted > | tags are pushed > `---- Your test above confirms that the description is correct and nothing is missing. "git push" pushes explicitly listed refspecs (or : as a default). It pushes tags (light and heavy) when asked to. "git pull" pulls tags if they can be reached from heads which are pulled. It pulls all tags only when asked to. In fact, the automatic following of tags (if they can be reached...) depends on the transport, because typically you want to clone everything if you clone locally but don't want all tags if you clone/pull from a remote. There is also a config "tagopt" for overriding this. It's mentioned but not really explained in "git tag"'s man page. So, "non-local" tags are the ones which can be reached from heads which you pull, and local ones are the others. I don't think lightweight tags are more local than tag objects (please correct me if I'm wrong; I think this needs more doc). It's just that the latter reside in the object db store whereas the former are simple refs under refs/tags. Michael -- 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
