From: Ryan Anderson <ryan@michonline.com>
To: Alejandro Bonilla <alejandro.bonilla@hp.com>
Cc: Dave Jones <davej@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: git fetching
Date: Thu, 29 Dec 2005 20:17:00 -0500 [thread overview]
Message-ID: <43B48A8C.8000708@michonline.com> (raw)
In-Reply-To: <20051230010151.GC12822@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]
Dave Jones wrote:
> On Thu, Dec 29, 2005 at 06:53:42PM -0600, Alejandro Bonilla wrote:
> > Why is it that when I git fetch, this particular part takes a long time?
> >
> > pack/pack-2dae6bb81ac4383926b1d6a646e3f73b130ba124.pack
> >
> > Normally, they go pretty fast, but when a new rc or final releases comes
> > up, it takes a lot.
>
> That file is ~100MB. That'll take a while to download compared to the rest,
> even on the fastest net connection :)
If you're carrying around a mostly current tree, you should probably not
use "rsync" (which is probably why you're seeing that pack line)
Run this:
sed -i.old -e 's/rsync/git/' .git/remotes/origin
and your pulls should go significantly faster.
(The file named "origin" might be in .git/branches/, also.)
You want the file to contain pretty much just this line:
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
Also, out of curiosity, do:
du -sh .git/objects/ .git/objects/pack/
You shouldn't see a .git/objects/pack/ much greater than 200 meg, in
fact, on freshly cloned tree it would only be about 100 meg:
http://www.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git/objects/pack/
--
Ryan Anderson
sometimes Pug Majere
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2005-12-30 1:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-30 0:53 git fetching Alejandro Bonilla
2005-12-30 1:01 ` Dave Jones
2005-12-30 1:17 ` Ryan Anderson [this message]
2005-12-30 7:13 ` Qi Yong
2005-12-30 9:42 ` Xavier Bestel
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=43B48A8C.8000708@michonline.com \
--to=ryan@michonline.com \
--cc=alejandro.bonilla@hp.com \
--cc=davej@redhat.com \
--cc=linux-kernel@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.