From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Emily Shaffer <nasamuffin@google.com>, ellie <el@horse64.org>,
rsbecker@nexbridge.com, git@vger.kernel.org
Subject: Re: With big repos and slower connections, git clone can be hard to work with
Date: Tue, 11 Jun 2024 08:12:12 -0700 [thread overview]
Message-ID: <xmqqh6dzy0mr.fsf@gitster.g> (raw)
In-Reply-To: <20240611063123.GB3248245@coredump.intra.peff.net> (Jeff King's message of "Tue, 11 Jun 2024 02:31:23 -0400")
Jeff King <peff@peff.net> writes:
> I think they serve two different purposes. A packfile URI does not have
> any connectivity guarantees. So it lets a server say "here's all the
> objects, except for XYZ which you should fetch from this URL". That's
> good for offloading pieces of a clone, like single large objects.
>
> Whereas bundle URIs require very little cooperation from the server.
> While a server can advertise bundle URIs, it doesn't need to know about
> the particular bundle a client grabbed. The client comes back with the
> usual have/want, just like any other fetching client.
Yes, a bundle being a self-contained "object-store + tips", it is
a much more suitable building block for offloading clone traffic.
next prev parent reply other threads:[~2024-06-11 15:12 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 23:28 With big repos and slower connections, git clone can be hard to work with ellie
2024-06-07 23:33 ` rsbecker
2024-06-08 0:03 ` ellie
2024-06-08 0:35 ` rsbecker
2024-06-08 0:46 ` ellie
2024-06-08 8:43 ` Jeff King
2024-06-08 9:40 ` ellie
2024-06-08 9:44 ` ellie
2024-06-08 10:38 ` Jeff King
2024-06-08 10:35 ` Jeff King
2024-06-08 11:05 ` ellie
2024-06-08 19:00 ` Junio C Hamano
2024-06-08 20:16 ` ellie
2024-06-10 6:46 ` Patrick Steinhardt
2024-06-10 19:04 ` Emily Shaffer
2024-06-10 20:34 ` Junio C Hamano
2024-06-10 21:55 ` ellie
2024-06-13 10:10 ` Toon claes
2024-06-11 6:31 ` Jeff King
2024-06-11 15:12 ` Junio C Hamano [this message]
2024-06-29 1:53 ` Sitaram Chamarty
2024-06-11 6:26 ` Jeff King
2024-06-11 19:40 ` Ivan Frade
2024-07-07 23:42 ` ellie
2024-07-08 1:27 ` rsbecker
2024-07-08 2:28 ` ellie
2024-07-08 12:30 ` rsbecker
2024-07-08 12:41 ` ellie
2024-07-08 14:32 ` Konstantin Khomoutov
2024-07-08 15:02 ` rsbecker
2024-07-08 15:14 ` ellie
2024-07-08 15:31 ` rsbecker
2024-07-08 15:48 ` ellie
2024-07-08 16:23 ` rsbecker
2024-07-08 17:06 ` ellie
2024-07-08 17:38 ` rsbecker
2024-07-08 16:09 ` Emanuel Czirai
2024-07-08 15:44 ` Konstantin Khomoutov
2024-07-08 16:27 ` rsbecker
2024-07-14 12:00 ` ellie
2024-07-24 6:42 ` ellie
2025-09-08 2:34 ` Ellie
2024-09-30 21:01 ` Ellie
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=xmqqh6dzy0mr.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=el@horse64.org \
--cc=git@vger.kernel.org \
--cc=nasamuffin@google.com \
--cc=peff@peff.net \
--cc=rsbecker@nexbridge.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).