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

Re: Pushing vs. alternates

From
Junio C Hamano <junkio@cox.net>
Date
Oct 24, 2006, 05:29 UTC
Message-ID
<7vmz7muvqu.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20061024035335.GW20017@pasky.or.cz>
Petr Baudis <pasky@ucw.cz> writes:
>   I don't have time to code that myself right now, so I'm just tossing
> an idea around - pushing to a directory with alternates set up should
> avoid sending objects that are already in the alternate object database.

That is probably only relevant for the first time, since subsequent pushes have refs from its own repository that tracks the tips of branches that was pushed for the last time.

And first time usage when you are initializing the repository with alternates, you have direct access to that repository (that's how you can set up alternates), you can as easily do the initial fetch/clone as well at that time.

So it might be a nice addition but I suspect it would not matter much in practice.

Previous: Petr BaudisNext: Shawn Pearce
Message 2 of 7 in “Pushing vs. alternates”
  1. Petr BaudisOct 24, 2006
  2. Junio C HamanoOct 24, 2006
  3. Shawn PearceOct 24, 2006
  4. Petr BaudisOct 24, 2006
  5. Junio C HamanoOct 24, 2006
  6. Petr BaudisOct 24, 2006
  7. Junio C HamanoOct 24, 2006

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.