From: Han-Wen Nienhuys <hanwen@xs4all.nl>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-fetch: Avoid reading packed refs over and over again
Date: Sat, 30 Dec 2006 20:04:23 +0100 [thread overview]
Message-ID: <4596B837.8030108@xs4all.nl> (raw)
In-Reply-To: <Pine.LNX.4.63.0612181329480.3635@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin escreveu:
>
> Here you have to check first, if len > 3. Strictly speaking, there should
> not be any line coming in which is shorter than 42 bytes. But I was
> recentely bitten by such an assuption...
>
> Overall, I like it. I even have the impression that this could actually
> open a way to build in fetch instead of relying on a POSIX conformant and
> fast shell for such a central part of git.
is there any chance of this going in GIT 1.5.0 ? It's not in the rc0 release.
--
Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen
next prev parent reply other threads:[~2006-12-30 19:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-17 19:52 [PATCH] git-fetch: Avoid reading packed refs over and over again Johannes Schindelin
2006-12-18 1:54 ` Junio C Hamano
2006-12-18 12:33 ` Johannes Schindelin
2006-12-30 19:04 ` Han-Wen Nienhuys [this message]
2006-12-30 19:24 ` Johannes Schindelin
2006-12-30 20:02 ` Han-Wen Nienhuys
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=4596B837.8030108@xs4all.nl \
--to=hanwen@xs4all.nl \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.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 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).