From: A Large Angry SCM <gitzilla@gmail.com>
To: Shawn Pearce <spearce@spearce.org>, git@vger.kernel.org
Subject: Re: Git files data formats documentation
Date: Sat, 05 Aug 2006 10:31:09 -0700 [thread overview]
Message-ID: <44D4D5DD.8070908@gmail.com> (raw)
In-Reply-To: <20060805162233.GA19909@spearce.org>
Shawn Pearce wrote:
> A Large Angry SCM <gitzilla@gmail.com> wrote:
>> This information may be useful for reading and writing the various Git
>> files.
> [snip]
>> # /* - - - - - - - - - - - - *\
>> # | This reflects version 3 pack files |
>> # \* - - - - - - - - - - - - */
> [snip]
>> # /* - - - - - - - - - - - - *\
>> # | This reflects version 2 pack files |
>> # \* - - - - - - - - - - - - */
>
> Thanks for taking the time to write these out. The pack delta
> formats were particularly helpful as it caused me to go back
> and look at the unpacking code in jgit.
>
> Apparently I wasn't handling the version 2 pack file correctly as I
> didn't support copy-from-result; I had an infinite loop if the base
> didn't decompress in one read (never happen right now, but could
> in the future); and apparently my insert opcode implementation was
> causing an infinite loop. Nasty bugs. I need to get more unit
> tests written apparently. :-)
Keep in mind that the git-core code for reading version 2 or version 3
pack files does _not_ handle copy-from-result correctly.
next prev parent reply other threads:[~2006-08-05 17:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-05 5:39 Git files data formats documentation A Large Angry SCM
2006-08-05 5:48 ` Jon Smirl
2006-08-05 6:51 ` Junio C Hamano
2006-08-05 19:30 ` Shawn Pearce
2006-08-05 21:56 ` A Large Angry SCM
2006-08-06 0:37 ` Junio C Hamano
2006-08-05 16:22 ` Shawn Pearce
2006-08-05 17:31 ` A Large Angry SCM [this message]
2006-08-05 18:41 ` Jakub Narebski
2006-08-05 20:15 ` A Large Angry SCM
2006-08-05 23:43 ` Jakub Narebski
2006-08-05 22:35 ` A Large Angry SCM
2006-08-16 16:55 ` Nicolas Pitre
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=44D4D5DD.8070908@gmail.com \
--to=gitzilla@gmail.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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).