From: Bryan Larsen <bryan@larsen.st>
To: git <git@vger.kernel.org>
Subject: large publicly accessible HTTP archive?
Date: Fri, 31 Oct 2008 13:07:01 -0400 [thread overview]
Message-ID: <490B3B35.60508@larsen.st> (raw)
In-Reply-To: <S1751776AbYJaQ5O/20081031165714Z+111@vger.kernel.org>
Hello,
I'm one of the maintainers of MacPorts git port.
A long time ago, we had problems pulling extremely large archives over
HTTP on PowerPC machines. By large, I mean on the order of 500
megabytes: I was testing using an embedded Linux distribution.
We "fixed" the problem by turning off CURL_MULTI and ignored the
problem. Yes, bad form, I know.
Our problems were against curl 7.16.2.
However, in recent git's, CURL_MULTI is required to do an HTTP push, so
we've had users complaining.
Curl is up to 7.19.0, they may have fixed our problem. Unfortunately,
the distribution I used for testing is gone now. Putting up a local
archive doesn't exhibit the problem either.
Is anybody aware of a very large HTTP accessible repository that
wouldn't mind me doing a few test pulls from? By large, I mean >500
megabytes of network traffic for a single pull.
thanks,
Bryan
next parent reply other threads:[~2008-10-31 17:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S1751776AbYJaQ5O/20081031165714Z+111@vger.kernel.org>
2008-10-31 17:07 ` Bryan Larsen [this message]
2008-10-31 19:01 ` large publicly accessible HTTP archive? Daniel Stenberg
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=490B3B35.60508@larsen.st \
--to=bryan@larsen.st \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox