Re: warning: no common commits - slow pull

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Daniel Barkalow
Date: Wednesday, February 27, 2008 - 12:28 pm

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*
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
warning: no common commits - slow pull, Len Brown, (Sun Feb 10, 6:07 pm)
Re: warning: no common commits - slow pull, Junio C Hamano, (Sun Feb 10, 6:44 pm)
Re: warning: no common commits - slow pull, Theodore Tso, (Sun Feb 10, 6:53 pm)
Re: warning: no common commits - slow pull, Len Brown, (Sun Feb 10, 7:39 pm)
Re: warning: no common commits - slow pull, Junio C Hamano, (Sun Feb 10, 7:49 pm)
Re: warning: no common commits - slow pull, Theodore Tso, (Sun Feb 10, 8:55 pm)
Re: warning: no common commits - slow pull, Florian Weimer, (Mon Feb 11, 8:54 am)
Re: warning: no common commits - slow pull, Nix, (Mon Feb 11, 2:13 pm)
Re: warning: no common commits - slow pull, Len Brown, (Fri Feb 15, 2:43 pm)
Re: warning: no common commits - slow pull, Johannes Schindelin, (Sat Feb 16, 2:22 pm)
Re: warning: no common commits - slow pull, Daniel Barkalow, (Sat Feb 16, 8:52 pm)
Re: warning: no common commits - slow pull, Johannes Schindelin, (Sun Feb 17, 7:57 am)
Re: warning: no common commits - slow pull, Daniel Barkalow, (Sun Feb 17, 10:46 am)
Re: warning: no common commits - slow pull, Junio C Hamano, (Sun Feb 17, 10:54 am)
Re: warning: no common commits - slow pull, Johannes Schindelin, (Sun Feb 17, 12:27 pm)
Re: warning: no common commits - slow pull, Daniel Barkalow, (Sun Feb 17, 1:41 pm)
Re: warning: no common commits - slow pull, Florian Weimer, (Mon Feb 25, 2:59 pm)
Re: warning: no common commits - slow pull, Daniel Barkalow, (Mon Feb 25, 4:32 pm)
Re: warning: no common commits - slow pull, Len Brown, (Tue Feb 26, 12:38 pm)
Re: warning: no common commits - slow pull, Nicolas Pitre, (Tue Feb 26, 1:47 pm)
Re: warning: no common commits - slow pull, Daniel Barkalow, (Tue Feb 26, 4:45 pm)
Re: warning: no common commits - slow pull, Junio C Hamano, (Tue Feb 26, 10:12 pm)
Re: warning: no common commits - slow pull, Junio C Hamano, (Tue Feb 26, 11:29 pm)
Re: warning: no common commits - slow pull, Daniel Barkalow, (Wed Feb 27, 12:28 pm)
Re: warning: no common commits - slow pull, Junio C Hamano, (Wed Feb 27, 1:53 pm)
Re: warning: no common commits - slow pull, Daniel Barkalow, (Wed Feb 27, 2:26 pm)
Re: warning: no common commits - slow pull, Shawn O. Pearce, (Wed Feb 27, 5:43 pm)
Re: warning: no common commits - slow pull, Shawn O. Pearce, (Thu Feb 28, 1:50 am)
Re: warning: no common commits - slow pull, Jon Loeliger, (Fri Feb 29, 7:44 am)
Re: warning: no common commits - slow pull, Daniel Barkalow, (Fri Feb 29, 10:14 am)