Many thanks to Greg Woods and Eric Siegerman for setting me straight and
giving me several helpful suggestions.
Here is the approach and a procedure that I would like to take. (This is
not to say that Eric's suggestions were inferior, but it is simply more
tailored to our intranet
On Sun, Sep 23, 2001 at 08:40:57AM -0500, Art Eschenlauer wrote:
Assumptions,
6. DS1L is a super-sandbox repository at DS1, which is to say that it
is where untested changes may be committed. Its hierarchy
maintained identically with that of GMSL.
Isn't this exactly the problem
On Fri, Sep 21, 2001 at 03:40:23PM -0500, Art Eschenlauer wrote:
We need to discover or learn about a method whereby changes checked
into one repository may be pulled into copies of that repository
located at our multiple other locations; in effect, each repository
must become the master for
Greetings!
We develop software using CVS as an SCM tool. Our developers are
located at multiple sites linked by a moderate-speed,
moderate-reliability network. CVSup seems like the tool to use to
replicate.
We need to discover or learn about a method whereby changes checked
into one repository
[ On Friday, September 21, 2001 at 15:40:23 (-0500), Art Eschenlauer wrote: ]
Subject: Bidirectional repository synchronization with CVSup - how?
We develop software using CVS as an SCM tool. Our developers are
located at multiple sites linked by a moderate-speed,
moderate-reliability
