From: "Shawn O. Pearce" <spearce@spearce.org>
To: Peter Eriksen <s022018@student.dtu.dk>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2] Add description of OFS_DELTA to the pack format description
Date: Sun, 6 Apr 2008 16:28:21 -0400 [thread overview]
Message-ID: <20080406202821.GN10274@spearce.org> (raw)
In-Reply-To: <20080406201907.GB7075@bohr.gbar.dtu.dk>
Peter Eriksen <s022018@student.dtu.dk> wrote:
>
> diff --git a/Documentation/technical/pack-format.txt b/Documentation/technical/pack-format.txt
> index aa87756..953c7ee 100644
> --- a/Documentation/technical/pack-format.txt
> +++ b/Documentation/technical/pack-format.txt
> @@ -103,10 +103,24 @@ Pack file entry: <+
> packed object data:
> If it is not DELTA, then deflated bytes (the size above
> is the size before compression).
> - If it is DELTA, then
> + If it is REF_DELTA, then
> 20-byte base object name SHA1 (the size above is the
> size of the delta data that follows).
> delta data, deflated.
> + If it is OFS_DELTA, then
> + n-byte offset (see below) counted from the type-byte
> + of the header of the ofs-delta entry.
Except that only a positive offset value is here, as it is always
a treated as a negative offset (you can only refer to a base that
was before you, as that is the only way to know the base's offset
in the pack).
> + (the size above is the size of the delta data
> + that follows).
> + delta data, deflated.
> +
> + offset encoding:
> + n bytes with MSB set in all but the last one.
> + The offset is then the number constructed by
> + concatenating the lower 7 bit of each byte, and
> + for n >= 2 adding 2^7 + 2^14 + ... + 2^(7*(n-1))
> + to the result.
Yes, that sounds correct.
--
Shawn.
next prev parent reply other threads:[~2008-04-06 20:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-06 13:47 [PATCH] Add description of OFS_DELTA to the pack format description Peter Eriksen
2008-04-06 19:07 ` Shawn O. Pearce
2008-04-06 20:19 ` [PATCH v2] " Peter Eriksen
2008-04-06 20:28 ` Shawn O. Pearce [this message]
2008-04-06 20:51 ` [PATCH v3] " Peter Eriksen
2008-04-06 22:26 ` Shawn O. Pearce
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=20080406202821.GN10274@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=s022018@student.dtu.dk \
/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).