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

[PATCH 0/2] thin-pack capability for send-pack/receive-pack

From
Carlos Martín Nieto <cmn@elego.de>
Date
Nov 6, 2013, 15:04 UTC
Message-ID
<1383750263-32495-1-git-send-email-cmn@elego.de>
Hi all,

This comes as a result of the discussion starting at [0] about git-push assuming that a server will always support thin packs. Most out there in fact do, but this isn't necessarily the case.

Some implementations may not have support for it yet, or the server might be running in an environment where it is not feasible for it to try to fill in the missing objects.

Jonathan and Duy mentioned that separate patches for receive-pack and send-pack could let us work around adding this at such a late stage, so here they are. The second patch can maybe lie in waiting for a while.

[0] http://thread.gmane.org/gmane.comp.version-control.git/235766/focus=236402
Carlos Martín Nieto (2):
  receive-pack: advertise thin-pack
  send-pack: only send a thin pack if the server supports it
 Documentation/technical/protocol-capabilities.txt | 20 +++++++++++++++-----
 builtin/receive-pack.c                            |  2 +-
 send-pack.c                                       |  2 ++
 3 files changed, 18 insertions(+), 6 deletions(-)
-- 
1.8.4.652.g0d6e0ce
Next: Carlos Martín Nieto
Message 1 of 10 in “thin-pack capability for send-pack/receive-pack”
  1. 0/2 thin-pack capability for send-pack/receive-packCarlos Martín Nieto, Nov 6, 2013
  2. 1/2 receive-pack: advertise thin-packCarlos Martín Nieto, Nov 6, 2013
  3. 2/2 send-pack: only send a thin pack if the server supports itCarlos Martín Nieto, Nov 6, 2013
  4. Junio C HamanoNov 6, 2013
  5. Carlos Martín NietoNov 6, 2013
  6. Junio C HamanoNov 6, 2013
  7. Jeff KingNov 6, 2013
  8. Shawn PearceNov 6, 2013
  9. Shawn PearceNov 6, 2013
  10. Carlos Martín NietoNov 23, 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.