From: Jeff Garzik <jeff@garzik.org>
To: Git Mailing List <git@vger.kernel.org>,
Junio C Hamano <junkio@cox.net>,
Linus Torvalds <torvalds@osdl.org>
Cc: "David S. Miller" <davem@davemloft.net>
Subject: git-clone failures abound
Date: Wed, 26 Jul 2006 00:38:46 -0400 [thread overview]
Message-ID: <44C6F1D6.5020208@garzik.org> (raw)
I've been seeing several reports lately, from different users on various
Linux platforms, with the same basic bug report
* "git:// clone of linus's repo times out after 10 minutes"
* someone says, "use rsync:// for the initial clone"
* "it works, thanks!"
People seems to note that this behavior only started recently. I wonder
if linux-2.6.git crossed some sort of size threshold that's too much for
kernel.org CPU load to bear? I wonder if git-clone is attempting to
delta-ify, when it really should just be sending the objects in bulk?
Jeff
next reply other threads:[~2006-07-26 4:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 4:38 Jeff Garzik [this message]
2006-07-26 5:02 ` git-clone failures abound Junio C Hamano
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=44C6F1D6.5020208@garzik.org \
--to=jeff@garzik.org \
--cc=davem@davemloft.net \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).