On Tue, 30 Mar 2010 20:54:09 +0000, "Robin H. Johnson" <robbat2@xxxxxxxxxx> wrote: > I'm trying to see about the state of automated mirroring git > repositories between different systems, eg. a private backend and a > public frontend, and ran into a catch between two possible options, each > with a downside. If there are other means besides these, I'm all ears > for them. You can mitigate the git caveats somewhat ... > git clone --mirror && git fetch: > -------------------------------- > How: > - Setup with: "git clone --mirror URL" > - Cronjob with: "git fetch" > Benefits: > - Extremely fast > - Light on traffic > Caveats: > - Branches and tags deleted in master persist in slaves :-( > - Seperate gc/repack needed on slaves. > > The traffic vs. deleted branches/tags is the main tradeoff here, esp. as > repos get larger. > > Can git-fetch perhaps be made to delete the branches/tags? I don't think that fetch can do it, but "git remote prune origin" will. You could also add "git gc --auto" to your cron script to deal with the repacking - I don't think fetch already does that ... -- Julian -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html