On Fri, 24 Aug 2007, Junio C Hamano wrote: > Daniel Barkalow <barkalow@xxxxxxxxxxxx> writes: > > > There seems to be an inconsistency between the fetch and tag over whether > > lightweight tags of non-commits are allowed. Fetch doesn't like them, but > > tag creates them without any particular fuss. > > Is your "fetch does not like them" about the automated > following? If you say "git fetch $remote tag $that_tag" there > shouldn't be any difference. > > And the difference in the automated following behaviour is > deliberate. Lightweight ones tend to be private "anchor point" > during development (these days we need that less often, thanks > to reflogs), and annotated ones, especially the signed kinds are > meant for public consumption. I get a bunch of: error: Object 0938d5832b4e40e6f440fa5c424c77b70714fb59 is a blob, not a commit lines. I think it's either in trying to decide whether they should be put in FETCH_HEAD or in trying to determine reachability through them. The server also seems to be unable to tell that I already have the blobs, and sends a pack of all of them each time I pull with tags. -Daniel *This .sig left intentionally blank* - 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
