Re: [CDSA-maintainers] Changes in CDSA CVS repository at SourceForge

[Dan N. <dn...@ca...>]

Dan Nuffer wrote:
> 
> I agree the best solution is to do this.  Let's do it this way:
> Step 1: Each maintainer commits any changes to cvs (or save a patch to
> apply later), deletes their local copy of cdsa checked out code, and
> then e-mails cds...@so... to let me know they've
> done it.
> Step 2: After I have received confirmation from Hugh, Afchine and Shafik
> I will delete all 1.1.1.1 revisions from cvs.
> Step 3: I will e-mail everyone letting them know it is done, and then
> everyone can check out the code again.
> 
> Sound good?
> 
> --Dan
> 

Okay, It's now done.
I ran into some problems (1), but I think it's all been fixed.  Please
re-check out the code and yell if there are any problems!  I have
already checked out the code and started a build, and things seem to be
going smoothly so far.

--Dan

(1) I deleted version 1.1.1.1, and then when I went to check out the
code to make sure everything worked, almost all the files were gone, and
cvs was giving me lots of error messages.  So, looking at the web cvs at
sourceforge, it said that the default branch was 1.1.1.1, so when trying
to check out files it was trying to get non-existent ones.  After lots
of reading man pages and cvs documentation, I discovered how to change
the default branch.  Unfortunately it wouldn't work recursively, so I
had to run the cvs command for each file.  This took most of the day
yesterday to do.  It still hadn't finished when I went home.  It looks
like everything is fine now :)