$ git clone --depth 1 git://repo.or.cz/alt-git.git tmp_cgit_5 Cloning into tmp_cgit_5... remote: Counting objects: 20234, done. remote: Compressing objects: 100% (9454/9454), done. remote: Total 20234 (delta 16355), reused 13587 (delta 10421) Receiving objects: 100% (20234/20234), 9.15 MiB | 1.17 MiB/s, done. Resolving deltas: 100% (16355/16355), done. $ cd tmp_cgit_5 $ git tag -l | grep 0.99 v0.99 Uhm. That is not a very shallow clone. The clone copied 20234 objects at 9.15 MiB... so its ~20 MiB lighter than a full clone. But nearly all of the tags exist, because the clone client is declaring want lines for them, making the server generate up to 1 commit back from the wanted tag. I know shallow support is the feature nobody wants to think about, but this just seems broken to me. Clients performing a shallow clone shouldn't be asking for tags... but they should be using the include-tag protocol option so that if they do happen to receive a tagged commit, the tag object will also be sent. -- Shawn. -- 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