From: Jean-Luc Herren <jlh@gmx.ch>
To: git@vger.kernel.org
Cc: Resul Cetin <Resul-Cetin@gmx.net>,
Nguyen Thai Ngoc Duy <pclouds@gmail.com>,
gentoo-scm@gentoo.org
Subject: Re: Optimizing cloning of a high object count repository
Date: Sat, 13 Dec 2008 17:44:07 +0100 [thread overview]
Message-ID: <4943E657.9040204@gmx.ch> (raw)
In-Reply-To: <200812131714.05472.Resul-Cetin@gmx.net>
Resul Cetin wrote:
> That would be a workaround but it doesn't explain why git.kernel.org deliveres
> torvalds repository without any notable counting and compressing time.
If I remember right, git.kernel.org is a quite beefy machine. But
then again it has a lot more traffic too. It might be interesting
to know what machine you're on, compared to git.kernel.org.
jlh
next prev parent reply other threads:[~2008-12-13 16:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-13 15:24 Optimizing cloning of a high object count repository Resul Cetin
2008-12-13 15:46 ` Nguyen Thai Ngoc Duy
2008-12-13 16:14 ` Resul Cetin
2008-12-13 16:44 ` Jean-Luc Herren [this message]
2008-12-13 18:20 ` Resul Cetin
2008-12-13 18:56 ` Nicolas Pitre
2008-12-13 21:50 ` Nicolas Pitre
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=4943E657.9040204@gmx.ch \
--to=jlh@gmx.ch \
--cc=Resul-Cetin@gmx.net \
--cc=gentoo-scm@gentoo.org \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).