From: "Martin Ågren" <martin.agren@gmail.com>
To: Ross Light <ross@zombiezen.com>
Cc: git@vger.kernel.org
Subject: [PATCH 1/2] pack-format.txt: define "varint" format
Date: Mon, 21 Dec 2020 08:54:58 +0100 [thread overview]
Message-ID: <42c6206b102cd97290fd9ad207bb39b20660064c.1608537234.git.martin.agren@gmail.com> (raw)
In-Reply-To: <cover.1608537234.git.martin.agren@gmail.com>
We define our varint format pretty much on the fly as we describe a pack
file entry. In preparation for referring to it in more places in this
document, define "varint" and refer to it.
Signed-off-by: Martin Ågren <martin.agren@gmail.com>
---
Documentation/technical/pack-format.txt | 17 +++++++++++++----
1 file changed, 13 insertions(+), 4 deletions(-)
diff --git a/Documentation/technical/pack-format.txt b/Documentation/technical/pack-format.txt
index f96b2e605f..42198de74c 100644
--- a/Documentation/technical/pack-format.txt
+++ b/Documentation/technical/pack-format.txt
@@ -55,6 +55,15 @@ Valid object types are:
Type 5 is reserved for future expansion. Type 0 is invalid.
+=== Variable-length integer encoding
+
+This document uses "varint" encoding of non-negative integers: From
+each byte, the seven least significant bits are used to form the
+resulting integer. As long as the most significant bit is 1, this
+process continues; the byte with MSB 0 provides the last seven bits.
+The seven-bit chunks are concatenated. Later values are more
+significant.
+
=== Deltified representation
Conceptually there are only four object types: commit, tree, tag and
@@ -196,10 +205,10 @@ Pack file entry: <+
1-byte size extension bit (MSB)
type (next 3 bit)
size0 (lower 4-bit)
- n-byte sizeN (as long as MSB is set, each 7-bit)
- size0..sizeN form 4+7+7+..+7 bit integer, size0
- is the least significant part, and sizeN is the
- most significant part.
+ n-byte size1 (varint encoding; present if MSB is set)
+ If the MSB is set, the size is size0 + 16*size1, otherwise
+ it is size0. (Equivalently, the entire packed object header
+ is a varint encoding of (size/16)*128 + type*16 + size%16.)
packed object data:
If it is not DELTA, then deflated bytes (the size above
is the size before compression).
--
2.30.0.rc1
next prev parent reply other threads:[~2020-12-21 7:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 17:07 Documentation errors for HTTP protocol v2 and packfile Ross Light
2020-12-21 7:54 ` [PATCH 0/2] pack-format.txt: document lengths at start of delta data Martin Ågren
2020-12-21 7:54 ` Martin Ågren [this message]
2020-12-21 21:40 ` [PATCH 1/2] pack-format.txt: define "varint" format Junio C Hamano
2020-12-29 22:41 ` Martin Ågren
2020-12-21 7:54 ` [PATCH 2/2] pack-format.txt: document lengths at start of delta data Martin Ågren
2020-12-23 4:40 ` [PATCH 0/2] " Ross Light
2020-12-29 22:43 ` [PATCH v2] pack-format.txt: document sizes " Martin Ågren
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=42c6206b102cd97290fd9ad207bb39b20660064c.1608537234.git.martin.agren@gmail.com \
--to=martin.agren@gmail.com \
--cc=git@vger.kernel.org \
--cc=ross@zombiezen.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 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).