From: Patrick Steinhardt <ps@pks.im>
To: "brian m. carlson" <sandals@crustytoothpaste.net>,
Milan Hauth <milahu@gmail.com>,
git@vger.kernel.org
Subject: Re: Git dumb HTTP protocol should work without update-server-info
Date: Mon, 8 Sep 2025 11:40:10 +0200 [thread overview]
Message-ID: <aL6kevExmhesoEWN@pks.im> (raw)
In-Reply-To: <aL2fn4j5uhrVWrDp@fruit.crustytoothpaste.net>
On Sun, Sep 07, 2025 at 03:07:11PM +0000, brian m. carlson wrote:
> I will also note that the dumb HTTP protocol doesn't work with reftable
> and there was some suggestion of removing it for Git 3.0. It certainly
> will not work out of the box with Git 3.0, since the default is
> reftable.
Yes, indeed. In theory though reftables could also be the solution to
the underlying issue: the client can be tought to read the "tables.list"
file and then fetch all tables listed therein. The result would be fully
consistent, unless any of the tables gets garbage collected. The client
would notice and abort the operation, after which it could restart the
operation.
In that case there would be no need for git-update-server-info(1)
anymore. The "tables.list" file sits in a well-known location,
identifies all other tables we have to download, and there are no
atomicity issues anymore.
The catch of course is that somebody would have to implement this :)
Patrick
next prev parent reply other threads:[~2025-09-08 9:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-07 11:24 Git dumb HTTP protocol should work without update-server-info Milan Hauth
2025-09-07 15:07 ` brian m. carlson
2025-09-07 17:23 ` Milan Hauth
2025-09-07 17:42 ` brian m. carlson
2025-09-08 9:40 ` Patrick Steinhardt [this message]
2025-09-08 14:43 ` Junio C Hamano
2025-09-09 5:26 ` Patrick Steinhardt
2025-09-08 0:05 ` Jeff King
2025-09-08 4:14 ` Junio C Hamano
2025-09-08 21:27 ` brian m. carlson
2025-09-09 1:35 ` Jeff King
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=aL6kevExmhesoEWN@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=milahu@gmail.com \
--cc=sandals@crustytoothpaste.net \
/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).