[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Move (merge) project from one repository to another (project exists
Re: Move (merge) project from one repository to another (project exists in both)
Tue, 7 Feb 2006 15:34:36 -0500
On 2/7/06, Paul Sander <address@hidden> wrote:
I'd look at some of the multi-site algorithms that people have applied
to CVS over the years, and apply one of them to the RCS files. Or just
map a branch in R_1 to the trunk of R_2 and do a series of co/ci
operations to copy the history over, applying tags as necessary. Then
use CVS normally to merge the top of the old R_2 trunk to the R_1
If you end up doing something like this yourself from scratch then my
rinfo program can help analyze the meta-data stored in the RCS files.
It's located at the following URL:
Neeto. I spent all weekend hacking away at a flex/bison RCS info
lexer/parser. I figured it would be a nice easy way to get my
feet wet with flex and bison...
Thanks for the reply.
On Feb 7, 2006, at 5:55 AM, Russ Sherk wrote:
> Any ideas?
> On 2 Feb 2006 05:18:35 -0800, Xapp <
>> Currently we have 2 repo's with the same project.R_1/mod_A,
>> R_2/mod_A.For some reason, R_1/mod_A was abandoned and development
>> proceded on R_2/mod_A.R_1 is our main repo and we want to move
>> R_2/mod_a to R_1.
>> I know that a project can be moved from repo to repo with the only
>> impact being to checked out copies , .Is it possible to move
>> R_2/mod_a to R_1/mod_a without losing history?Or would it be better
>> to move the unwanted project out of the way and replace (copy) it with
>> the new one?
>>  - Moving a project -
>>  - Renaming directories -
Paul Sander | "When a true genius appears in the world, you may
address@hidden | know him by this sign: that all the dunces are in
| confederacy against him." -- Jonathan Swift,
Info-cvs mailing list