On Wed, Jun 29, 2022 at 08:40:40PM +0000, Derrick Stolee via GitGitGadget wrote: > diff --git a/Documentation/technical/bundle-uri.txt b/Documentation/technical/bundle-uri.txt > new file mode 100644 > index 00000000000..a0230a902a4 > --- /dev/null > +++ b/Documentation/technical/bundle-uri.txt > +Implementation Plan > +------------------- > + > +This design document is being submitted on its own as an aspirational > +document, with the goal of implementing all of the mentioned client > +features over the course of several patch series. Here is a potential > +outline for submitting these features: > + > +1. Integrate bundle URIs into `git clone` with a `--bundle-uri` option. > + This will include a new `git fetch --bundle-uri` mode for use as the > + implementation underneath `git clone`. The initial version here will > + expect a single bundle at the given URI. > + > +2. Implement the ability to parse a bundle list from a bundle URI and > + update the `git fetch --bundle-uri` logic to properly distinguish > + between `bundle.mode` options. Specifically design the feature so > + that the config format parsing feeds a list of key-value pairs into the > + bundle list logic. > + > +3. Create the `bundle-uri` protocol v2 verb so Git servers can advertise s/verb/command/ or s/verb/request/ 'bundle-uri' is not a verb, but even if it were, the protocol v2 documentation talks only about commands and requests, but never mentions a single "verb". > + bundle URIs using the key-value pairs. Plug into the existing key-value > + input to the bundle list logic. Allow `git clone` to discover these > + bundle URIs and bootstrap the client repository from the bundle data. > + (This choice is an opt-in via a config option and a command-line > + option.)
