From: Shawn Pearce <spearce@spearce.org>
To: Nicolas Pitre <nico@cam.org>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH 1/2] Allow pack header preprocessing before unpack-objects/index-pack.
Date: Tue, 31 Oct 2006 15:08:41 -0500 [thread overview]
Message-ID: <20061031200841.GC23671@spearce.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0610311400180.11384@xanadu.home>
Nicolas Pitre <nico@cam.org> wrote:
> On Tue, 31 Oct 2006, Shawn Pearce wrote:
>
> > However if the caller consumes the pack header from the input stream
> > then its no longer available for unpack-objects or index-pack --stdin,
> > both of which need the version and object count to process the stream.
> >
> > This change introduces --pack_header=ver,cnt as a command line option
> > that the caller can supply to indicate it has already consumed the
> > pack header and what version and object count were found in that
> > header. As this option is only meant for low level applications
> > such as receive-pack we are not documenting it at this time.
>
> This breaks index-pack, and unpack-objects with OBJ_OFS_DELTA, if
> --pack-header is used. The header is not accounted in the pack's offset
> and therefore every object's offset is wrong.
>
> What about this patch instead? This makes things much simpler IMHO.
Agreed. The idea you are using here came to me in my sleep last
night; I didn't have time to look at it until now however. You just
beat me to posting it. :-)
--
next prev parent reply other threads:[~2006-10-31 20:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-31 7:56 [PATCH 1/2] Allow pack header preprocessing before unpack-objects/index-pack Shawn Pearce
2006-10-31 19:33 ` Nicolas Pitre
2006-10-31 20:08 ` Shawn Pearce [this message]
2006-10-31 23:51 ` Junio C Hamano
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=20061031200841.GC23671@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=nico@cam.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).