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

On Friday 27 August 2004 10:19, Jamis Buck wrote:
> Sean O'Dell wrote:
> > 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.
>
> Well, mucking with the CVS repository directly isn't really an option,
> since I don't have direct access to the RubyForge machines. :( If this
> really were the difference between v1 and v2 I might bug Tom about
> reorganizing my repo, but since its not, I think I'll just go with the
> tag-and-delete option.

If you use a linux desktop, you might try Cervisia.  I don't use it for 
day-to-day work, but whenever I've had to do major restructuring to a 
repository that I had no shell access to, it really helped.  It's a GUI so it 
really helps you see what is what and where everything is, and when you 
delete something, it not only removes the file, it issues the CVS remove 
command.  It has saved me a lot of headache a couple times.

 Sean O'Dell