From: Christian Couder Date: Mon, 16 Mar 2026 11:21:23 GMT Subject: Re: [GSoC] Proposal: Complete and extend the remote-object-info command for git cat-file Message-ID: In-Reply-To: Hi Pablo, On Sat, Mar 14, 2026 at 7:31 PM Pablo wrote: > #### 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. > 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.