Re: bundles discovery and clones

[Jeff King <peff@peff.net>]

On Tue, Jun 11, 2024 at 07:14:48AM -0400, matthew sporleder wrote:

> > I don't think the server side is well documented, but peeking at the
> > code, I think you want this on the server:
> >
> >   git config uploadpack.advertiseBundleURIs true
> >   git config bundle.version 1
> >   git config bundle.mode any
> >   git config bundle.foo.uri https://example.com/your.bundle
> >
> > And then the clients need to tell Git that they allow bundle transfers:
> >
> >   git config --global transfer.bundleURI true
> [...]
> 
> It wasn't clear to me what the <id> (bundle.foo in your case) referred
> to. Where did 'foo' come from?

It is not clear to me either. ;) I don't know if <id> is meaningful,
beyond grouping related bundle options into a single stanza. In my
example, "foo" is just a made-up word you can replace with whatever you
want. It is visible to clients at the protocol layer, though I don't
think Git actually shows it to the user.

> Anyway if people are taking suggestions for UX I'll give my $0.02:
> git clone --try-bundle, with --bundle-uri overriding, to allow the
> client to ask the server for bundles that satisfy their request.

Yeah, I looked for something similar at first but couldn't find it. You
can do:

  git -c transfer.bundleURI clone ...

-Peff