From: chenxitwo <chenxitwo@126.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: git <git@vger.kernel.org>
Subject: Re: Git: How to keep multiple bare repos in sync?
Date: Wed, 13 May 2015 15:01:42 +0800 [thread overview]
Message-ID: <2015051315014048836362@126.com> (raw)
In-Reply-To: xmqq4mnhccti.fsf@gitster.dls.corp.google.com
not remote sync.
We have three teams to participate in the same project, and is located in different places. Bandwidth that between the two of our teams is not enough. Three teams have their own git server. Like this kind of situation, how should handle?
chenxitwo
From: Junio C Hamano
Date: 2015-05-13 12:37
To: chenxitwo
CC: git
Subject: Re: Git: How to keep multiple bare repos in sync?
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.
next prev parent reply other threads:[~2015-05-13 7:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 4:09 Git: How to keep multiple bare repos in sync? chenxitwo
2015-05-13 4:37 ` Junio C Hamano
2015-05-13 7:01 ` chenxitwo [this message]
2015-06-03 1:55 ` chenxitwo
2015-06-03 4:10 ` David Lang
2015-05-14 13:11 ` Konrad Scherer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2015051315014048836362@126.com \
--to=chenxitwo@126.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).