From: Stefan Roese <sr@denx.de>
To: Dan Aloni <da-x@monatomic.org>
Cc: Daniel Barkalow <barkalow@iabervon.org>,
git@vger.kernel.org, Junio C Hamano <junkio@cox.net>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH] Limit the number of requests outstanding in ssh-fetch.
Date: Tue, 4 Oct 2005 09:46:48 +0200 [thread overview]
Message-ID: <200510040946.49509.sr@denx.de> (raw)
In-Reply-To: <20051004071638.GA23725@localdomain>
On Tuesday 04 October 2005 09:16, Dan Aloni wrote:
> > Lightly tested; I reduced the limit to 5, and pulled a small tree
> > successfully with some of the requests being completed early. I didn't
> > have the test case to verify that a limit of 100 is sufficiently low, but
> > handwaving suggests that it should be.
>
> Good, it seems that your patch works alright with the local Linux complete
> database fetch.
Works for me too (on a big ssh fetch, which stalled always without this
patch).
Best regards,
Stefan
prev parent reply other threads:[~2005-10-04 7:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-04 4:24 [PATCH] Limit the number of requests outstanding in ssh-fetch Daniel Barkalow
2005-10-04 7:16 ` Dan Aloni
2005-10-04 7:46 ` Stefan Roese [this message]
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=200510040946.49509.sr@denx.de \
--to=sr@denx.de \
--cc=barkalow@iabervon.org \
--cc=da-x@monatomic.org \
--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 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.