Thanks for the input guys. We could do an automatic sync with manual
notifications on merge conflicts (would probably be rare), but I think we
will smplify our setup like Konstantin suggests.
* We have many readers of the repo in zone two, so we set up a clone
--mirror as a read only repo in zone two which mirrors zone one
* We make ssh available to the few clients in zone two that needs write to
the repo in zone one (transparent forwarding
http://sshmenu.sourceforge.net/articles/transparent-mulithop.html through a
jump host, or exceptions in the firewall)
On Thursday, 29 August 2013 00:01:21 UTC+2, Philip Oakley wrote:
> ----- Original Message -----
> Sent: Wednesday, August 28, 2013 10:38 PM
> Subject: Re: [git-users] Two way mirroring because over network zones
> > That said, is the two sides won't talk you will get conflicts, so do
> > expect the tool to do everything ;-)
> Oops, Should read:
> That said, if the two sides won't talk you will get conflicts, so don't
> expect the tool to do everything ;-)
> > Do have a look at how git itself is developed with a layered approach
> > to the synchronization problem; 'master' is never rewound, 'next' is
> > occasionally rewound at choreographed points, 'pu' (potential
> > updates) is often rewound, so folks have a good handle on levels of
> > stability and where their patches have progressed to.
> > Philip
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/groups/opt_out.