From: Masaya Suzuki <firstname.lastname@example.org>
Cc: Masaya Suzuki <email@example.com>
Subject: [PATCH v2] doc: describe Git bundle format
Date: Fri, 31 Jan 2020 14:18:00 -0800 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
The bundle format was not documented. Describe the format with ABNF and
explain the meaning of each part.
Signed-off-by: Masaya Suzuki <email@example.com>
Changes from v1:
* Update the ABNF definition so that prerequisites come before references.
* Adopt Junio's suggestion on the semantics section.
* State that the receiver MUST ignore the comments in the prereqs.
* Change "you" to "the receiver" and "the sender" (I wonder if this should be
"writer" and "reader").
Documentation/technical/bundle-format.txt | 41 +++++++++++++++++++++++
1 file changed, 41 insertions(+)
create mode 100644 Documentation/technical/bundle-format.txt
diff --git a/Documentation/technical/bundle-format.txt b/Documentation/technical/bundle-format.txt
new file mode 100644
@@ -0,0 +1,41 @@
+= Git bundle v2 format
+The Git bundle format is a format that represents both refs and Git objects.
+We will use ABNF notation to define the Git bundle format. See
+protocol-common.txt for the details.
+bundle = signature *prerequisite *reference LF pack
+signature = "# v2 git bundle" LF
+prerequisite = "-" obj-id SP comment LF
+comment = *CHAR
+reference = obj-id SP refname LF
+pack = ... ; packfile
+A Git bundle consists of three parts.
+* "Prerequisites" lists the objects that are NOT included in the bundle and the
+ receiver of the bundle MUST already have, in order to use the data in the
+ bundle. The objects stored in the bundle may refer to prerequisite objects and
+ anything reachable from them and/or expressed as a delta against prerequisite
+* "References" record the tips of the history graph, iow, what the receiver of
+ the bundle CAN "git fetch" from it.
+* "Pack" is the pack data stream "git fetch" would send, if you fetch from a
+ repository that has the references recorded in the "References" above into a
+ repository that has references pointing at the objects listed in
+ "Prerequisites" above.
+In the bundle format, there can be a comment following a prerequisite obj-id.
+This is a comment and it has no specific meaning. The sender of the bundle MAY
+put any string here. The receiver of the bundle MUST ignore the comment.
next prev parent reply other threads:[~2020-01-31 22:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-30 22:58 [PATCH] doc: describe Git bundle format Masaya Suzuki
2020-01-31 13:56 ` Johannes Schindelin
2020-01-31 20:38 ` Junio C Hamano
2020-01-31 21:49 ` Masaya Suzuki
2020-01-31 23:01 ` Junio C Hamano
2020-01-31 23:57 ` Masaya Suzuki
2020-02-04 18:20 ` Junio C Hamano
2020-01-31 22:18 ` Masaya Suzuki [this message]
2020-01-31 23:06 ` [PATCH v2] " Junio C Hamano
2020-02-07 20:42 ` [PATCH v3] " Masaya Suzuki
2020-02-07 20:44 ` Masaya Suzuki
2020-02-07 20:59 ` Junio C Hamano
2020-02-07 22:21 ` Masaya Suzuki
2020-02-08 1:49 ` Junio C Hamano
2020-02-12 22:13 ` Masaya Suzuki
2020-02-12 22:43 ` Junio C Hamano
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:
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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 read-only IMAP folder(s) and NNTP newsgroup(s).