git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Milan Hauth <milahu@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Git dumb HTTP protocol should work without update-server-info
Date: Sun, 7 Sep 2025 17:42:43 +0000	[thread overview]
Message-ID: <aL3EE7dLMuj6ONZQ@fruit.crustytoothpaste.net> (raw)
In-Reply-To: <CAGiEHCvFnhZRXwNVRyzQ4ABi3p0Opdo8+draXoDu5p1R6HZn1Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]

On 2025-09-07 at 17:23:28, Milan Hauth wrote:
> > HTTP push
> 
> im only talking about "read" operations:
> 
> git ls-remote
> git fetch
> git pull

Yes, as I said, reading directories is only possible with WebDAV since
HTTP doesn't offer native directory listing.  However, we don't use
WebDAV for fetches and other read operations and not all web servers
support it.  We get better web server support in many cases by requiring
that the server side do the work of updating the lists of packs and
refs.

Without some way to list directories, you cannot in the general case
iterate over the refs and packs in the file system without a manifest,
so creating a manifest is what update-server-info does.

This is also why most tools which provide HTTP access in the file system
require WebDAV, since it isn't very useful to have a file system where
you can't list directories.  (We abandoned directory-less file systems
in the early DOS and Macintosh days.)
-- 
brian m. carlson (they/them)
Toronto, Ontario, CA

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2025-09-07 17:42 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 [this message]
2025-09-08  9:40   ` Patrick Steinhardt
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=aL3EE7dLMuj6ONZQ@fruit.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=git@vger.kernel.org \
    --cc=milahu@gmail.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).