Re: [PATCH v4 5/8] transport: add client side capability to request object-info

From: Junio C Hamano <gitster@pobox.com>
Date: May 4, 2022, 15:50 UTC
Message-ID: <xmqq8rrhnvph.fsf@gitster.g>
In-Reply-To: <20220503231558.4172288-1-jonathantanmy@google.com>

Jonathan Tan <jonathantanmy@google.com> writes:

> RTT more than necessary. We could just determine if the server supports
> the attributes we want by using capabilities (without needing to send
> the request to check).

Hmph.  capabilities may cut in both ways, though.

Those clients that are not interested in object-info at all (which are the majority of case where people clone, fetch or ls-remote), they do not even need to know what kind of object attributes the object-info command is prepared to report, and they would appreciate not having to spend any extra byte in the capability-advertisement.

Of course, for object-info clients, having it upfront does make things simpler.

So...

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.