git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [GSoC] Proposal: Complete and extend the remote-object-info command for git cat-file

From
Christian Couder <christian.couder@gmail.com>
Date
Mar 16, 2026, 11:21 UTC
Message-ID
<CAP8UFD2PDqrpV-Y8EntJxfaRDP7aBXr47nQcVPeX=80yiLAoHw@mail.gmail.com>
In-Reply-To
<CAN5EUNQdNtPq1mEBUXOjRJ_t2n=cSUS9dz+HUfqbFjrjZVoGLQ@mail.gmail.com>
Hi Pablo,
On Sat, Mar 14, 2026 at 7:31 PM Pablo <pabloosabaterr@gmail.com> wrote:
Show 9 quoted lines
> #### Backward Compatibility
>
> There are four possible scenarios to happen between client and server:
>
> 1. **The server doesn't know type (new client but old server)**:
>
>    After receiving the server capabilities, a client will only request
> what the server advertises. The `allow_list` would handle this,
> returning an empty string when the server doesn't support it.

This is not very clear and maybe answering the following questions could help clarify:

1) What is returning an empty string. Is it the `allow_list`, the
client, the server or something else?
2) And what is actually reported to the user (en error, a warning, nothing)?
3) Also is it what is implemented in Eric's v11, or what you suggest
implementing?
> 2. **The server knows type but the client doesn't (new server but old client)**:
>
>    Following `gitprotocol-v2.adoc`, "Clients must ignore all unknown
> keys", it will ignore type, and request only the known capabilities.
Questions 2) and 3) above might be relevant here too.
Show 11 quoted lines
> 3. **Both know type (new client and new server)**:
>
>    Server advertises type, client requests it and gets the type data.
>
> 4. **Both know type but protocol middleware doesn't (new client, new
> server but old middleware)**:
>
>    If a server advertises type but client doesn't receive type, a
> client won't ask for anything unadvertised, if a client asks for type
> but the server doesn't receive it, it will only return the known
> capabilities.
Questions 2) and 3) above might be relevant here too.
[...]
> Thanks for reading my proposal and considering my application. I'm
> very excited about this opportunity,
Thanks for your proposal.
Best.
Previous: Chandra PratapNext: Karthik Nayak
Message 5 of 10 in “[GSoC] Proposal: Complete and extend the remote-object-info command for git cat-file”
  1. PabloMar 13, 2026
  2. Chandra PratapMar 14, 2026
  3. PabloMar 14, 2026
  4. Chandra PratapMar 15, 2026
  5. Christian CouderMar 16, 2026
  6. Karthik NayakMar 16, 2026
  7. PabloMar 18, 2026
  8. [GSoC v3] Proposal: Complete and extend the remote-object-info command for git cat-filePablo Sabater, Mar 16, 2026
  9. PabloMar 18, 2026
  10. PabloApr 12, 2026

Read the whole thread, see it on lore, or plain text.

$ 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.