From: Petr Baudis <pasky@suse.cz>
To: wa1ter@myrealbox.com
Cc: git@vger.kernel.org
Subject: Re: http protocol, cloning git.git, fails (too many open files)
Date: Mon, 14 Nov 2005 02:09:40 +0100 [thread overview]
Message-ID: <20051114010940.GQ30496@pasky.or.cz> (raw)
In-Reply-To: <Pine.LNX.4.64.0511131625490.32662@x2.ybpnyarg>
Dear diary, on Mon, Nov 14, 2005 at 01:42:33AM CET, I got a letter
where wa1ter@myrealbox.com said that...
>
>
> On Sun, 13 Nov 2005, walt wrote:
>
> > On Sat, 2005-11-12 at 15:21 -0800, Junio C Hamano wrote:
> > [...]
> > > However, one thing puzzles me. I just tried to reproduce it by
> > > doing this:
> > >
> > > $ rm -fr git-http
> > > $ ulimit -n 16
> > > $ git clone http://www.kernel.org/pub/scm/git/git.git git-http
> > >
> > > and it did not fail on my Linux box...
>
> > I've never seen it on Linux...
>
> Aha! I do indeed see it on linux with ulimit -n 64 but *only* when I
> do the clone with cg-clone. When I use 'git clone' it works just fine.
>
> 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, while git-clone uses some custom logic
for cloning ("dumb http clone"). (In fact, is there a point in carrying
it further now that git-http-fetch got as smart as it got? You'll have
less code, and more importantly see bugs in the fetchers otherwise only
I see with Cogito. ;-)
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.
next prev parent reply other threads:[~2005-11-14 1:09 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 [this message]
2005-11-14 1:52 ` Junio C Hamano
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=20051114010940.GQ30496@pasky.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=wa1ter@myrealbox.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.