From: Masaya Suzuki <email@example.com> To: Junio C Hamano <firstname.lastname@example.org> Cc: Git Mailing List <email@example.com> Subject: Re: [PATCH] doc: describe Git bundle format Date: Fri, 31 Jan 2020 13:49:53 -0800 Message-ID: <CAJB1erXnNe0yGvL+wgU9RXAA6Vyx7T2dwM9NgCmUChOtL102NQ@mail.gmail.com> (raw) In-Reply-To: <firstname.lastname@example.org> On Fri, Jan 31, 2020 at 12:38 PM Junio C Hamano <email@example.com> wrote: > > Masaya Suzuki <firstname.lastname@example.org> writes: > > > The bundle format was not documented. Describe the format with ABNF and > > explain the meaning of each part. > > Thanks. > > > > > Signed-off-by: Masaya Suzuki <email@example.com> > > --- > > Documentation/technical/bundle-format.txt | 40 +++++++++++++++++++++++ > > 1 file changed, 40 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 > > index 0000000000..dbb80225b5 > > --- /dev/null > > +++ b/Documentation/technical/bundle-format.txt > > @@ -0,0 +1,40 @@ > > += Git bundle v2 format > > + > > +The Git bundle format is a format that represents both refs and Git objects. > > + > > +== Format > > + > > +We will use ABNF notation to define the Git bundle format. See > > +protocol-common.txt for the details. > > + > > +---- > > +bundle = signature references pack > > +signature = "# v2 git bundle" LF > > Good. "signature" is the name used by bundle.c::create_bundle() to > call this part. > > > +references = *(prerequisite / ref) LF > > This allows prereq and ref can come inter-mixed, but I think we show > all prerequisites first before refs. Based on bundle.c::parse_bundle_header(), I infer that this can be mixed. If that's not intended, this can be changed to have prerequisites first. > > > +prerequisite = "-" obj-id SP comment LF > > +comment = *CHAR > > Do readers know what CHAR consists of? Anything other than NUL and > LF? RFC 5234 defines core rules (https://tools.ietf.org/html/rfc5234#appendix-B.1), and these CHAR etc are defined there. It should be OK to use these rules. > > > +ref = obj-id SP refname LF > > OK. > > "prerequisite" and "ref" are both used in bundle.c::create_bundle(), > so calling these parts with these names is consistent with the code. > "head" is also a good name for the latter as "git bundle list-heads" > is the way the end-users access them from outside. > > > + > > +pack = ... ; packfile > > +---- > > + > > +== Semantics > > + > > +A Git bundle consists of three parts. > > + > > +* Prerequisites: Optional list of objects that are not included in the bundle > > + file. A bundle can reference these prerequisite objects (or it can reference > > + the objects reachable from the prerequisite objects). The bundle itself > > + might not contain those objects. > > While not incorrect per-se, the above misses the more important > points (and defers the description to a later paragraph). It is > better to describe what it means to have prereqs upfront. > > > +* References: Mapping of ref names to objects. > > +* Git objects: Commit, tree, blob, and tags. These are included in the pack > > + format. > > + > > Match the name you used to descibe the parts in the earlier ABNF > description, so that the correspondence is clear to the readers. > You somehow used "references" to mean both prereqs and heads, but in > the above you are describing only "heads" under the label of > "references". Yes. It should match with the ABNF definition above. I usually use "heads" to mean "references under refs/heads/*" (not sure if this is true for other people). Since a bundle can contain tags etc., using "heads" here seems confusing. With prerequisites and references split you mentioned above, I think I can make ABNF and this semantics section consistent in terms of wording. bundle = signature *prerequisite *ref LF pack prerequisite = "-" obj-id SP comment LF comment = *CHAR reference = obj-id SP refname LF pack = ... ; packfile The terms ("prerequisite" and "reference") are consistent with bundle.h::ref_list. > > Perhaps something like this? > > * "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 prerequiste objects and anything > reachable from them and/or expressed as a delta against > prerequisite objects. I want to make sure the meaning of prerequisites. 1. Are they meant for a delta base? Or are they meant to represent a partial/shallow state? If these prerequisites are used as a delta base, the receiver of the bundle MUST have them. If these prerequisites are the indicators of the shallowness or the partialness of the repository, the pack data would have complete data in terms of deltification (e.g. all objects in the pack file can be undeltified with just the pack file), and the bundle can be treated as a shallow-cloned/partially-cloned repository snapshot. From what I can see from bundle.c, I think it's an indicator of a delta base, not an indicator of a shallow/partial state, but I want to make sure. 2. Do they need to be commits? Or can they be any object type? From what I can see, it seems that they should always be commits. 3. Does the receiver have to have all reachable objects from prerequisites? My understanding is "Yes, the receiver must have all reachable objects from prerequisites." This means that if a receiver has a shallow-cloned repository, they might not be able to proceess a bundle with prerequisites. The bundle's pack part can deltify against the objects that exist beyond the shallow depth. > > * "Heads" 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 "Heads" above into a repository that has references > pointing at the objects listed in "Prerequisites" above. I'll adopt this in the next patch. > > > +If a bundle contains prerequisites, it means the bundle has a thin pack and the > > +bundle alone is not enough for resolving all objects. When you read such > > +bundles, you should have those missing objects beforehand. > > With the above rewrite, this paragraph is unneeded. > > > +In the bundle format, there can be a comment following a prerequisite obj-id. > > +This is a comment and it has no specific meaning. When you write a bundle, you > > +can put any string here. When you read a bundle, you can ignore this part. > > Is it "you can"? At least the last one should be "readers of a > bundle MUST ignore the comment", I think. I'll change this to MUST.
next prev parent reply other threads:[~2020-01-31 21:50 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-01-30 22:58 Masaya Suzuki 2020-01-31 13:56 ` Johannes Schindelin 2020-01-31 20:38 ` Junio C Hamano 2020-01-31 21:49 ` Masaya Suzuki [this message] 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 ` [PATCH v2] " Masaya Suzuki 2020-01-31 23:06 ` 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
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 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 \ --in-reply-to=CAJB1erXnNe0yGvL+wgU9RXAA6Vyx7T2dwM9NgCmUChOtL102NQ@mail.gmail.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.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
email@example.com list mirror (unofficial, one of many) This inbox may be cloned and mirrored by anyone: git clone --mirror https://public-inbox.org/git git clone --mirror http://ou63pmih66umazou.onion/git git clone --mirror http://czquwvybam4bgbro.onion/git git clone --mirror http://hjrcffqmbrq6wope.onion/git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V1 git git/ https://public-inbox.org/git \ firstname.lastname@example.org public-inbox-index git Example config snippet for mirrors. Newsgroups are available over NNTP: nntp://news.public-inbox.org/inbox.comp.version-control.git nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git nntp://news.gmane.io/gmane.comp.version-control.git note: .onion URLs require Tor: https://www.torproject.org/ code repositories for the project(s) associated with this inbox: https://80x24.org/mirrors/git.git AGPL code for this site: git clone https://public-inbox.org/public-inbox.git