Junio C Hamano <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED] (Eric W. Biederman) writes: > >> What we care about are the tag objects, those are the only kind >> that are verifiable and usable remotely. >> >> Now that I know we do not pull tags currently with any of the >> optimized transports, I would suggest taking the list of commit >> objects we are transporting and for each commit look in the >> remote repo/refs/tags and transferring every tag object we can find >> that refers to that commit. > > I think if we have discovery mechanism of remote tags/heads, we > do not need anything else. You _could_ say something like: > > $ git-list-remote --tags linux-2.6 > 9e734775f7c22d2f89943ad6c745571f1930105f v2.6.12-rc2 > 26791a8bcf0e6d33f43aef7682bdb555236d56de v2.6.12 > ... > a339981ec18d304f9efeb9ccf01b1f04302edf32 v2.6.13-rc3 > $ git-list-remote --tags linux-2.6 | > while read sha1 tag; > do > git fetch linux-2.6 tag $tag > done
Actually looking a little deeper unless I have misread the code git-fetch-pack at least will only ask for commit objects so git fetch will never return a tag object. I have yet to find where it git-fetch-pack actually prints objects out so I still may be something. Eric - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html