[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: sync repositories

From: Ronald Landheer
Subject: RE: sync repositories
Date: Tue, 13 Aug 2002 11:19:53 +0200

Hello all,

  I've been following this discussion with some interest, as I have more
or less the same problem as mr Verhoeven. It seems, though, that there 
is no real solution to this problem without planning ahead before you 
get into trouble with the two separate repositories?
  I kinda liked the idea of making a branch out of one of the two repositories, 
but I'm wondering how that would work internally (in the 
repository files) as what I'm carrying around on a CD is not a set of 
diffs, but a tarball of the repository itself.
  For the moment, I have more than one repository on the same machine (I 
actually have four of them), one of which is read/write, the rest is 
read-only. This basically means I keep the repositories from the other 
sites in tact, read-only and I check out the latest version of the off-
site repository in another working directory specifying a the CVSROOT of 
one of the read-only repositories. It leaves the use of the off-site 
version optional to the project manager.
  It works pretty well: I keep the revision history of all of the 
repositories, I don't touch the repositories themselves and I have 
access to all versions of all projects. All I have to do to update one 
of the sites is overwrite the copies of the other repositories with new 
  I would be interested in a solution keeping only one repository, and I 
could start carrying diffs around in stead of repositories, but for the 
moment, this solution seems to be the best one for me - and might be an 
idea for mr Verhoeven as well..


Ronald Landheer

-----Original Message-----
From: address@hidden [mailto:address@hidden Behalf Of
Paul Sander
Sent: Friday, August 09, 2002 11:02 PM
To: address@hidden; address@hidden
Subject: Re: sync repositories

>--- Forwarded mail from address@hidden

>On Fri, Aug 09, 2002 at 12:50:06PM -0700, Paul Sander wrote:
>> Each site owns its own trunk.  Each site creates a branch that is used for
>> importing from the other site(s); these branches map to the trunk(s) at the
>> remote site(s).  No local commits are permitted on the import branches.
>> Each site keeps a list of branches to export to the other site(s), and
>> tracks the latest exported versions on each export branch.

>Interesting approach.  With some scripting, it could actually

Of course it will work.  You have no faith!  ;-)

>Geez, it sounds like a CVS-based (partial) implementation of your
>old EMFS thingie :-)

This design is way better than EMFS, actually.  It keeps the original
changes at each site on separate branches, so they're easier track and
isolate if necessary.  EMFS allows the definitive sources to get out of
synch with the remote copies, which can't happen with a versioning system
(provided the branch mastership conventions are enforced strictly).

>--- End of forwarded message from address@hidden

Info-cvs mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]