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

Re: Is anyone working on a next-gen Git protocol?

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 10, 2012, 20:46 UTC
Message-ID
<7vlifeawd5.fsf@alter.siamese.dyndns.org>
In-Reply-To
<035A66D9-FAF0-48EE-B161-7D0CAD92F2FB@zib.de>
Steffen Prohaska <prohaska@zib.de> writes:
Show 5 quoted lines
> I've recently discovered that the current protocol can be amazingly
> inefficient when it comes to transferring binary objects.  Assuming two
> repositories that are in sync.  After a 'git checkout --orphan && git
> commit', a subsequent transfers sends all the blobs attached to the new
> commit, although the other side already has all the blobs.

I do not think it has anything to do with binary, but what you deserve from using orphan, where you declared that the history does not have anything to do with the original.

If both of your repositories had the two paralle lines of these histories as branches, the transfer would have went well with or without binary objects.

Previous: Steffen ProhaskaNext: Philip Oakley
Message 9 of 12 in “Is anyone working on a next-gen Git protocol?”
  1. Ævar Arnfjörð BjarmasonOct 7, 2012
  2. Ilari LiusvaaraOct 7, 2012
  3. Jeff KingOct 7, 2012
  4. Junio C HamanoOct 7, 2012
  5. Junio C HamanoOct 22, 2012
  6. Andreas EricssonOct 8, 2012
  7. Junio C HamanoOct 8, 2012
  8. Steffen ProhaskaOct 10, 2012
  9. Junio C HamanoOct 10, 2012
  10. Philip OakleyOct 10, 2012
  11. Nguyen Thai Ngoc DuyOct 11, 2012
  12. Shawn PearceOct 11, 2012

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.