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

Re: [PATCH] send-pack: don't send a thin pack when the server doesn't support it

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Oct 8, 2013, 22:22 UTC
Message-ID
<20131008222215.GI9464@google.com>
In-Reply-To
<CACsJy8AHAbDuz3yhsjJfRQUGg1zzx6qqoAf=1oNhbX1xPVithg@mail.gmail.com>
Duy Nguyen wrote:
Show 5 quoted lines
> Or maybe it's not that late. How about you go with your patch and add
> thin-pack capability to receive-pack too?
>
> When new "git push" is used against old server, thin pack is disabled.
> But that's not a big deal (I hope).

Could we have separate patches to introduce the server-side capability and then to request it in the client? That way, people with old servers can apply the patch introducing the capability if they want.

The new meaning of the "thin-pack" capability should also be documented in Documentation/technical/protocol-capabilities.txt.

Done that way and with enough time between the server advertising the capability and the client looking for it, it seems like a good idea.

My two cents, Jonathan

Previous: Duy NguyenNext: Carlos Martín Nieto
Message 5 of 6 in “send-pack: don't send a thin pack when the server doesn't support it”
  1. send-pack: don't send a thin pack when the server doesn't support itCarlos Martín Nieto, Oct 8, 2013
  2. Duy NguyenOct 8, 2013
  3. Carlos Martin NietoOct 8, 2013
  4. Duy NguyenOct 8, 2013
  5. Jonathan NiederOct 8, 2013
  6. Carlos Martín NietoOct 19, 2013

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.