From: Junio C Hamano <junkio@cox.net>
To: Nick Hengeveld <nickh@reactrix.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Add support for parallel HTTP transfers
Date: Thu, 06 Oct 2005 17:51:53 -0700 [thread overview]
Message-ID: <7virwa5ety.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20051007000041.GH15593@reactrix.com> (Nick Hengeveld's message of "Thu, 6 Oct 2005 17:00:41 -0700")
Nick Hengeveld <nickh@reactrix.com> writes:
> About that "-r" arg - seems like it should be something else as -r is
> used elsewhere in git to enable recursion. "-c" was my first thought,
> but that's used to fetch commit objects.
Well, I'd suggest just to hardcode a reasonable value to be a
good net citizen, and not make it configurable. Four, perhaps?
OTOH, we may want to have an option to disable parallel from the
command line (I think -r 1 would mean that with yours).
If we really want to have the number of parallel configurable,
and -r implies recursive as you say, maybe '-j' to mimic
parallel make?
next prev parent reply other threads:[~2005-10-07 0:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 21:44 [PATCH] Add support for parallel HTTP transfers Nick Hengeveld
2005-10-06 20:07 ` Daniel Barkalow
2005-10-07 0:00 ` Nick Hengeveld
2005-10-07 0:51 ` Junio C Hamano [this message]
2005-10-07 4:56 ` Nick Hengeveld
2005-10-07 5:15 ` Junio C Hamano
2005-10-07 16:23 ` Daniel Barkalow
2005-10-07 17:01 ` Junio C Hamano
2005-10-07 17:22 ` Nick Hengeveld
2005-10-07 18:08 ` Junio C Hamano
2005-10-07 22:39 ` Daniel Barkalow
2005-10-10 16:48 ` Jon Loeliger
2005-10-07 17:41 ` Daniel Barkalow
2005-10-07 18:08 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2005-10-06 18:54 Nick Hengeveld
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=7virwa5ety.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=nickh@reactrix.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).