Re: warning: no common commits - slow pull

[Daniel Barkalow <barkalow@iabervon.org>]

Correcting the transport code is important (and should probably be done in 
transport.c, if possible), but I think we're being a bit silly in 
autofollowing tags anyway. If we decide to fetch T due to having T^{}, we 
should tell the remote up front that we have T^{}, before we mention 
anything else, because it's obviously true and it's also absolutely 
certain to make the remote immediately do the right thing. It's silly to 
decide to fetch T because we will only need that one object, and then not 
instantly tell the server we only need that one object. (And, as luck 
would have it, yesterday I wrote code to cause for_each_ref return some
specific values in addition to and before the actual stored refs.)

Of course, we shouldn't do this until we make the transport code more 
correct, because it's certain to hide any possible bug there.

Am I missing something in my analysis?

	-Daniel
*This .sig left intentionally blank*