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

Re: Git: How to keep multiple bare repos in sync?

From
Junio C Hamano <gitster@pobox.com>
Date
May 13, 2015, 04:37 UTC
Message-ID
<xmqq4mnhccti.fsf@gitster.dls.corp.google.com>
In-Reply-To
<2015051312090840845945@126.com>
chenxitwo <chenxitwo@126.com> writes:
> There are three git server(bare repos), but i don't know to solve the
> problem that how to keep these git servers in sync.
rsync?

The problem is under-specified. Is there one of them that is authoritative and that the other ones should match its progress? If so, perhaps push from the authoritative one to the other two with "push --mirror" (or have the other ones "fetch --mirror")?

If you are allowing people to push into any of them randomly,
then there is no general solution.  If I push an update to 'master'
of instance A while you update the same 'master' branch of instance
B, somebody has to reconcile the divergence between the two by
creating a merge, and that can possibly conflict, needing human
intervention to resolve.
Previous: chenxitwoNext: chenxitwo
Message 2 of 6 in “Git: How to keep multiple bare repos in sync?”
  1. chenxitwoMay 13, 2015
  2. Junio C HamanoMay 13, 2015
  3. chenxitwoMay 13, 2015
  4. chenxitwoJun 3, 2015
  5. David LangJun 3, 2015
  6. Konrad SchererMay 14, 2015

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.