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

Re: Maintaining site-wide clones

From
Sitaram Chamarty <sitaramc@gmail.com>
Date
Jan 8, 2009, 17:22 UTC
Message-ID
<slrngmcdj4.i8d.sitaramc@sitaramc.homelinux.net>
In-Reply-To
<alpine.LNX.1.00.0901081129500.19665@iabervon.org>
On 2009-01-08, Daniel Barkalow <barkalow@iabervon.org> wrote:
> Is there a good way of handling a setup where the canonical repository is 
> in some slow foreign system and you want a lot of git clones? I've been 
> using a bare repository that I import into and clone, but then I need to 
> go to the bare repository to update anything, which is vaguely annoying.
Why?  You can push to it too?
I don't have your use case but if I did, I'd do this:
 - everyone clones from the local mirror
 - one person clones the slow foreign system at whatever
   interval he thinks appropriate, and pushes to the local
   mirror
 - (or the local mirror can do this via cron)

This works fine if you can sort of judge the average frequency of updates, and not getting some of them *immediately* is not earth shattering for local developers.

If the slow foreign system lets you put in a post-commit hook that'll be even easier -- no more guesswork!

Previous: Daniel Barkalow
Message 2 of 2 in “Maintaining site-wide clones”
  1. Daniel BarkalowJan 8, 2009
  2. Sitaram ChamartyJan 8, 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.