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

Re: Use alternate GIT servers to share traffic

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Mar 25, 2009, 22:57 UTC
Message-ID
<alpine.DEB.1.00.0903252356160.26370@intel-tinevez-2-302>
In-Reply-To
<200903252145.30226.thomas@koch.ro>
Hi,
On Wed, 25 Mar 2009, Thomas Koch wrote:
Show 18 quoted lines
> we host a public GIT repository on our high availability company 
> cluster. Cloning the repo causes a trafic volume of 326 MB. We'd like to 
> avoid that much trafic while still leaving the GIT repo where it is.
> 
> I could imagine the following conversation between the GIT client and
> server:
> 
> Client: Wanna clone!
> Server: You're welcome. Please note, that while I serve the most current
> state, you can get objects much faster from my collegue Server
> CHEAPHOST.
> Client: Thank you. Will take all the objects I can get from CHEAPHOST
> and come back if I should need anything else!
> 
> The enduser should not need to specify anything, but only the regular
> git clone EXPENSIVEHOST line.
> 
> Your thoughts?
That sounds a lot like the mirror-sync idea.

Ciao, Dscho

Previous: Thomas KochNext: Andrew Wang
Message 2 of 4 in “Use alternate GIT servers to share traffic”
  1. Thomas KochMar 25, 2009
  2. Johannes SchindelinMar 25, 2009
  3. Andrew WangMar 26, 2009
  4. Samuel Lucas Vaz de MelloMar 26, 2009

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.