From: Junio C Hamano <junkio@cox.net>
To: Petr Baudis <pasky@suse.cz>
Cc: git@vger.kernel.org
Subject: Re: http protocol, cloning git.git, fails (too many open files)
Date: Sun, 13 Nov 2005 17:52:35 -0800 [thread overview]
Message-ID: <7v64qw807w.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20051114010940.GQ30496@pasky.or.cz> (Petr Baudis's message of "Mon, 14 Nov 2005 02:09:40 +0100")
Petr Baudis <pasky@suse.cz> writes:
> Dear diary, on Mon, Nov 14, 2005 at 01:42:33AM CET, I got a letter
> where wa1ter@myrealbox.com said that...
>>
>> So, what does cogito do differently that accounts for more open files?
>
> Cogito uses the same logic and underlying GIT fetching commands for
> cloning as well as for fetching,...
Ah, you are absolutely right. I've forgotten about that "dumb
http support" in git-clone.sh. That was done back when packs
were introduced but http-fetch was not told about them as a
stop-gap measure.
No wonder we do not see the same problem from git-clone. Thanks
for reminding me.
next prev parent reply other threads:[~2005-11-14 1:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-12 22:25 http protocol, cloning git.git, fails (too many open files) Randal L. Schwartz
2005-11-12 23:21 ` Junio C Hamano
2005-11-14 0:01 ` walt
2005-11-14 0:42 ` wa1ter
2005-11-14 1:09 ` Petr Baudis
2005-11-14 1:52 ` Junio C Hamano [this message]
2005-11-14 13:09 ` wa1ter
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=7v64qw807w.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
/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).