Re: warning: no common commits - slow pull

> On Sunday 09 March 2008, Daniel Barkalow wrote:
> > Try this. I'm not at all sure that it's doing what I want, but it passes 
> > all the current tests, and it should only affect your test case if it's 
> > actually right.
> 
> Seems to resolve that problem for me ... well timed, in terms of RC5!
> 
> But some stuff still looks a bit fishy.  See this RC4 --> RC5 pull:
> 
>   remote: Counting objects: 1329, done.
>   remote: Compressing objects: 100% (276/276), done.
>   remote: Total 908 (delta 749), reused 760 (delta 631)
>   Receiving objects: 100% (908/908), 146.35 KiB | 40 KiB/s, done.
>   Resolving deltas: 100% (749/749), completed with 287 local objects.
>   remote: Counting objects: 1330, done.
>   remote: Compressing objects: 100% (277/277), done.
>   remote: Total 909 (delta 749), reused 760 (delta 631)
>   Receiving objects: 100% (909/909), 146.63 KiB | 38 KiB/s, done.
>   Resolving deltas: 100% (749/749), completed with 287 local objects.
>   From git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6
>    * [new tag]         v2.6.25-rc5 -> v2.6.25-rc5
>   Updating 29e8c3c..cdeeeae
>   Fast forward
>   Auto packing your repository for optimum performance. You may also
>   run "git gc" manually. See "git help gc" for more information.
>   ...
> 
> That's pretty typical:  two count/compress/receive/resolve passes,
> with almost an identical shape and size.  Every time I see that, I
> suspect that most of the second one should not be needed...