Nguyễn Thái Ngọc Duy <pclouds@xxxxxxxxx> writes: > This could also be applied for normal clones. But I don't think > there are many use cases for it, enough to deserve new --no-tags > option. Correct. > We should also fetch a single branch, but because branches are > usually less crowded and stay close the tip, they do not produce too > many extra objects. Let's leave it until somebody yells up. Probably this is needed. > We should also fetch tags that reference to downloaded objects. I do not think this has much merit. The usual tag-following rules AFAIK assumes that if you have the commit C then you ought to have all the ancestors of C, which does not apply at all for the shallow hack to begin with, and if you make the rule apply for the shallow hack, you would end up slurping the objects that are needed only for ancient versions, which would defeat the objective of this patch, no? It also is my understanding that the shallow hack is almost always used with a depth of one, not a range, like "git archive | tar xf -", so if anything, I would say a single-branch cloning has much higher priority than following tags. Will queue on 'pu'. 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