Junio C Hamano <junkio@xxxxxxx> writes: > What if (I know, this discussion does not belong here until > 1.5.0 final) we had a "reverse" database that keeps track of > what tag references which object, and "git rev-list" knows how > to exploit it? That is, just like generating a list of objects > that are reachable with --objects option, if we can add a new > option --with-tag very cheaply to list tag objects that would > reach what are in the generated list of objects? > ... > Just an idle thought. Nah, that would not work. Please disregard. The thing is, you cannot sanely traverse and transfer objects that have such reverse connectivity. The other end can annotate a commit long after you acquired it, and trying to make git-fetch to retrieve newly created annotations would mean breaking "things reachable from your local refs are complete and there is nothing missing from them" invariant. Pushing into somebody else after annotating an old commit that already exists at the other end has the same issue. - 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