From: Florian Weimer <fw@deneb.enyo.de>
To: git@vger.kernel.org
Subject: Re: warning: no common commits - slow pull
Date: Mon, 25 Feb 2008 22:59:38 +0100 [thread overview]
Message-ID: <87ablod7ed.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <200802151643.30232.lenb@kernel.org> (Len Brown's message of "Fri, 15 Feb 2008 16:43:30 -0500")
* Len Brown:
> [lenb@d975xbx2 linus (master)]$ git pull
> remote: Counting objects: 649, done.
> remote: Compressing objects: 100% (106/106), done.
> remote: Total 513 (delta 417), reused 503 (delta 407)
> Receiving objects: 100% (513/513), 116.67 KiB, done.
> Resolving deltas: 100% (417/417), completed with 103 local objects.
> warning: no common commits
> remote: Counting objects: 710725, done.
> remote: Compressing objects: 100% (125738/125738), done.
> remote: Total 710725 (delta 589584), reused 704450 (delta 584029)
> Receiving objects: 100% (710725/710725), 172.71 MiB | 1073 KiB/s, done.
> Resolving deltas: 100% (589584/589584), done.
>>From git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6
Same here, but on a slow DSL line, so I had to hit ^C:
fw@deneb:~/src/linux/linux-2.6$ git pull
remote: Counting objects: 94176, done.
remote: Compressing objects: 100% (17486/17486), done.
remote: Total 83287 (delta 70429), reused 78218 (delta 65712)
Receiving objects: 100% (83287/83287), 18.66 MiB | 478 KiB/s, done.
Resolving deltas: 100% (70429/70429), completed with 7457 local objects.
warning: no common commits
remote: Counting objects: 53267
^C
This is Debian's 1:1.5.4.2-2 GIT version.
next prev parent reply other threads:[~2008-02-25 22:00 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 1:07 warning: no common commits - slow pull Len Brown
2008-02-11 1:44 ` Junio C Hamano
2008-02-17 3:52 ` Daniel Barkalow
2008-02-17 14:57 ` Johannes Schindelin
2008-02-17 17:46 ` Daniel Barkalow
2008-02-17 17:54 ` Junio C Hamano
2008-02-17 19:27 ` Johannes Schindelin
2008-02-17 20:41 ` Daniel Barkalow
2008-02-11 1:53 ` Theodore Tso
2008-02-11 2:39 ` Len Brown
2008-02-11 2:49 ` Junio C Hamano
2008-02-11 3:55 ` Theodore Tso
2008-02-15 21:43 ` Len Brown
2008-02-16 21:22 ` Johannes Schindelin
2008-02-25 21:59 ` Florian Weimer [this message]
2008-02-25 23:32 ` Daniel Barkalow
2008-02-26 19:38 ` Len Brown
2008-02-26 20:47 ` Nicolas Pitre
2008-02-26 23:45 ` Daniel Barkalow
2008-02-27 5:12 ` Junio C Hamano
2008-02-27 6:29 ` Junio C Hamano
2008-02-27 19:28 ` Daniel Barkalow
2008-02-27 20:53 ` Junio C Hamano
2008-02-27 21:26 ` Daniel Barkalow
2008-02-28 0:43 ` Shawn O. Pearce
2008-02-28 8:50 ` Shawn O. Pearce
2008-02-29 14:44 ` Jon Loeliger
2008-02-29 17:14 ` Daniel Barkalow
2008-02-28 0:47 ` Junio C Hamano
2008-02-28 15:53 ` Daniel Barkalow
2008-02-28 16:10 ` [PATCH] Always use the current connection's remote ref list in git protocol Daniel Barkalow
2008-02-28 17:52 ` warning: no common commits - slow pull Junio C Hamano
2008-02-28 18:36 ` Daniel Barkalow
2008-02-11 15:54 ` Florian Weimer
2008-02-11 21:13 ` Nix
-- strict thread matches above, loose matches on Subject: below --
2008-03-07 1:35 David Brownell
2008-03-08 1:22 ` Daniel Barkalow
2008-03-08 22:48 ` David Brownell
2008-03-08 22:58 ` Daniel Barkalow
2008-03-08 23:25 ` David Brownell
2008-03-08 23:27 ` Daniel Barkalow
2008-03-09 18:47 ` Daniel Barkalow
2008-03-10 17:18 ` David Brownell
2008-03-10 17:40 ` Daniel Barkalow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ablod7ed.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.