From: "Adam Kropelin" <akropel1@rochester.rr.com>
To: "Daniel Barkalow" <barkalow@iabervon.org>
Cc: "Tony Luck" <tony.luck@gmail.com>, <git@vger.kernel.org>
Subject: Re: [PATCH] Get commits from remote repositories by HTTP
Date: Sat, 16 Apr 2005 18:52:42 -0400 [thread overview]
Message-ID: <014a01c542d6$ff3e6180$03c8a8c0@kroptech.com> (raw)
In-Reply-To: Pine.LNX.4.21.0504161844040.30848-100000@iabervon.org
Daniel Barkalow wrote:
> On Sat, 16 Apr 2005, Adam Kropelin wrote:
>> How about building a file list and doing a batch download via 'wget
>> -i /tmp/foo'? A quick test (on my ancient wget-1.7) indicates that
>> it reuses connectionss when successive URLs point to the same server.
>
> You need to look at some of the files before you know what other
> files to get. You could do it in waves, but that would be excessively
> complicated to code and not the most efficient anyway.
Ah, yes. Makes sense. How about libcurl or another http client library,
then? Minimizing dependencies on external libraries is good, but writing a
really robust http client is a tricky business. (Not that you aren't up to
it; I just wonder if it's the best way to spend your time.)
--Adam
next prev parent reply other threads:[~2005-04-16 23:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-16 22:03 [PATCH] Get commits from remote repositories by HTTP Daniel Barkalow
2005-04-16 22:17 ` Martin Mares
2005-04-16 22:43 ` Daniel Barkalow
2005-04-16 22:24 ` Tony Luck
2005-04-16 22:33 ` Daniel Barkalow
2005-04-16 22:42 ` Adam Kropelin
2005-04-16 22:45 ` Daniel Barkalow
2005-04-16 22:52 ` Adam Kropelin [this message]
2005-04-17 3:16 ` tony.luck
2005-04-18 18:41 ` tony.luck
2005-04-18 18:47 ` Petr Baudis
2005-04-18 20:48 ` tony.luck
2005-04-16 22:32 ` Jan-Benedict Glaw
2005-04-16 22:37 ` Daniel Barkalow
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='014a01c542d6$ff3e6180$03c8a8c0@kroptech.com' \
--to=akropel1@rochester.rr.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=tony.luck@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 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.