On Fri, Aug 09, 2002 at 10:48:04AM -0700, Mike Ayers wrote:
I have to sync two CVS repositories located on two non-
connected networks. (yep, this means tape/CDROM transports,
I know it sounds silly).
This was discussed a couple of months ago, and a few approaches
were offered.
Now we have
On Thu, 10 Oct 2002, Eric Siegerman wrote:
Now we have to do the same thing. Not full synchronization,
actually -- every revision, log message, and tag replicated. All
we really need is that two sites be able to work on the same
modules without stepping on each others' feet, and without
:
Sent by:Subject: Re: sync
repositories
[EMAIL PROTECTED
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
I thought the idea here was to propogate version histories between multiple
repositories, not to keep multiple sandboxes in synch.
The method you propose does the latter, and doesn't accomodate local changes
to both sandboxes. It also provides no means to transfer other stuff such
as RCS states
On Mon, Aug 19, 2002 at 12:12:45PM -0700, Paul Sander wrote:
I thought the idea here was to propogate version histories between multiple
repositories, not to keep multiple sandboxes in synch.
The method you propose does the latter, and doesn't accomodate local changes
to both sandboxes. It
- and might be an
idea for mr Verhoeven as well..
Greetz!
Ronald Landheer
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Paul Sander
Sent: Friday, August 09, 2002 11:02 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: sync repositories
I have to sync two CVS repositories located on two non-
connected networks. (yep, this means tape/CDROM transports,
I know it sounds silly). I was wondering if there is a
better way than creating incremental tar files on both sides
and applying them on the other side. Luckily, the chances
Zieg, Mark wrote:
I have to sync two CVS repositories located on two non-
connected networks. (yep, this means tape/CDROM transports,
I know it sounds silly). I was wondering if there is a
better way than creating incremental tar files on both sides
and applying them on the other side.
I have to sync two CVS repositories located on two non-
connected networks.
If you MUST do this (and it is almost certain that you do
not need to, but that's another story)
I assume that you've never had to develop under DOD-enforced contract
requirements, or you wouldn't have written
There has been a fair amount of discussion about this topic in the past,
and I believe that someone has a working implementation that follows this
model:
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
Zieg, Mark wrote:
I have to sync two CVS repositories located on two non-
connected networks.
If you MUST do this (and it is almost certain that you do
not need to, but that's another story)
I assume that you've never had to develop under DOD-enforced contract
requirements, or you
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
--- Forwarded mail from [EMAIL PROTECTED]
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
14 matches
Mail list logo
