From: Sean O'Dell <sean@...>
Date: 2004-08-28T01:42:26+09:00
Subject: Re: [OT] CVS question

On Thursday 26 August 2004 21:33, Jamis Buck wrote:
>
> I just finished rewriting Copland, almost from the ground up. I'll be
> announcing the new version soon(ish), but I need to get it into CVS.
> Now, there's already an existing implementation of Copland in CVS, but
> I'd (obviously) like to replace it with the new version.
>
> What is the best way to go about this? Right now, I'm leaning towards
> doing a "cvs delete" on the existing implementation, and then checking
> in the new implementation on top of it. Thus, the existing version
> history is maintained, etc. Is there a better way to do this?

Don't try and do too much through CVS; it's a massive pain to reorganize a 
project through CVS.  Instead, edit the CVS repository directly.

If Copland was working on major version 1 before, just go into the repository, 
create a new directory named v1 in the copland dir, and mv everything into 
it.  It's really that simple.  Then you should 'cvs co copland/v1' where you 
develop and work on that copy.

Then in your new version, get rid of all your CVS directories and 'cvs import 
copland/v2 yourname start' and then 'cvs co copland/v2' where you want to 
work on it.

Some of those CVS commands are pseudo'd, but you get the idea.  Be sure to 
match the ownership and permissions so you can access everything from your 
user account.

 Sean O'Dell