[Top][All Lists]

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

Re: Keeping multiple CVS repositories in sync

From: Donald Sharp
Subject: Re: Keeping multiple CVS repositories in sync
Date: Wed, 10 Jul 2002 14:30:35 -0400
User-agent: Mutt/

On Wed, Jul 10, 2002 at 02:12:47PM -0400, Eric Siegerman wrote:
> On Wed, Jul 10, 2002 at 12:24:04PM -0500, Jay Yarbrough wrote:
> > It would appear for anyone who truly needs multiple repositories kept in 
> > sync,
> > that CVS is an unacceptable tool.  This is most unfortunate.
> Correct.  Various kludges have been suggested on this list, and
> maybe even used successfully -- but they're all kludges.
> Fundamentally, CVS expects there to be one repo, and it expects
> users to be connected to it when they do CVS operations.
> Disconnected operation is limited to the most trivial kind: check
> out a sandbox; take the laptop home (for e.g.) but don't do any
> CVS operations; bring the laptop back to work, plug it into the
> network, and commit.
> > Our need is to have them use an SCM tool that can support multiple 
> > synchronized
> > repositories.
> Bitkeeper ( claims to do this.  Not free,
> unfortunately, unless you're willing to live with all your commit
> logs being published.  I've never used it, so can't vouch for it,
> but it might be worth a look.

I've poked around in bitkeeper enough to know that it does 
have this ability.  You can also buy versions of bitkeeper that
don't require the commit log publishing at bitkeepers home

Basically each bitkeeper repository is loosely analagous to 
a branch in cvs.  When you create a new bk repository you 
specify it's parent and you also specify the relationships
that the bk repository has with other bk repositories.  You
then have the ability to push and pull change sets to other
bk repositories.  The ability to update the bk repository
is of course predicated upon a network connection ;)

> --
> |  | /\
> |-_|/  >   Eric Siegerman, Toronto, Ont.        address@hidden
> |  |  /
> Anyone who swims with the current will reach the big music steamship;
> whoever swims against the current will perhaps reach the source.
>       - Paul Schneider-Esleben
> _______________________________________________
> Info-cvs mailing list
> address@hidden

reply via email to

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