Re: warning: no common commits - slow pull
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Feb 17, 2008, 17:54 UTC
- Message-ID
- <7vhcg71n9u.fsf@gitster.siamese.dyndns.org>
- In-Reply-To
- <alpine.LSU.1.00.0802171449230.30505@racer.site>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
Show 11 quoted lines
> On Sat, 16 Feb 2008, Daniel Barkalow wrote: > >> I wonder if the problem is that something isn't getting reinitialized >> for the second connection. It's not a separate invocation of fetch-pack, >> and I can't say for sure that it's sending the right info to the server >> when the statics in builtin-fetch-pack.c are left over from the earlier >> call. This would particularly explain the information that hitting >> ctrl-c and trying again fixes it. > > Oh, that should be it! After all, the code in get_rev() in > builtin-fetch-pack.c marks commits as SEEN and COMMON and POPPED.
I seem to be slow today, but how does that explain that the problem is reported only by Len so far?