From: Linus Torvalds <torvalds@osdl.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux v2.6.16-c2
Date: Fri, 3 Feb 2006 10:11:02 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0602031007420.4630@g5.osdl.org> (raw)
In-Reply-To: <43E39932.4000001@lwfinger.net>
On Fri, 3 Feb 2006, Larry Finger wrote:
>
> I know you must have a good reason to switch to the 'pack' form in the git
> tree, but I'm curious. I did a git pull late yesterday, which was "normal",
> and another this morning when I saw that 2.6.16-rc2 was posted. I was quite
> surprised to download 110 MB of data to get roughly 150 changed lines.
Don't use rsync (or http) access unless you have to.
Try using "git://git.kernel.org/" instead.
Now, it may be that if we have lots of people using it, the CPU usage of
the server-side effort will go through the roof, and we'll have to come up
with something else (most likely meaning having some mirrors also run
git-daemon, so that the CPU overhead can be pushed out too).
The point being that you shouldn't see the packing as even an issue (it
should be a per-repository decision). The fact that it shows up is because
of using non-git-aware protocols.
Linus
next prev parent reply other threads:[~2006-02-03 18:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-03 17:56 Larry Finger
2006-02-03 18:11 ` Linus Torvalds [this message]
2006-02-03 18:25 ` Larry Finger
2006-02-03 19:57 ` Paolo Ornati
2006-02-03 20:38 ` Larry Finger
2006-02-03 21:01 ` Linus Torvalds
2006-02-03 21:11 ` Larry Finger
2006-02-03 23:50 ` Ryan Anderson
2006-02-03 23:59 ` Linus Torvalds
2006-02-04 0:35 ` Diego Calleja
2006-02-04 2:16 ` Linus Torvalds
2006-02-04 14:14 ` Diego Calleja
-- strict thread matches above, loose matches on Subject: below --
2006-02-03 6:36 Linus Torvalds
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=Pine.LNX.4.64.0602031007420.4630@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=Larry.Finger@lwfinger.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®