Vinod Damaraju wrote, On 07/13/2008 07:40 PM:
Larry,
Thank you for your reply. I do not have control over the CVS version on
the
Linux server i.e., cannot upgrade it nor replace it with CVSNT. If I use
the
remote CVS server, a signifcant functionality of the conversion tool
would
not work. I am looking for specific answers about the changes in
repository
file formats between CVSNT and CVS 1.11.xx so that I can account for
those
changes in my process ..
Do you have control over the conversion machine?
i.e., could you install a cygwin setup and use the cvs from that (which is
built from the Unix cvs sources) to do the conversion, and then move the
files to the Unix machine?
an alternative, which may loose some of the change data, might be cvssuck:
http://cvs.m17n.org/~akr/cvssuck/
http://freshmeat.net/projects/cvssuck/
the method I would go with it is:
do the conversion to cvsnt as you have done,
fire up a cvsnt binary as server (if you were on Unix set
CVS_SERVER=/path/to/cvsnt ) and cvssuck the data to normal cvs.
Then see if enough data followed you through whole process, if yes, then
move it to your real cvs server.
Thanks,
Vinod Damaraju
----- Original Message ----- From: "Larry Jones"
<address@hidden>
To: <address@hidden>
Cc: <address@hidden>
Sent: Wednesday, July 09, 2008 6:31 PM
Subject: Re: CVSNT versus CVS
address@hidden writes:
CVS server was on Linux and was CVS 1.11.2.
That is *ancient* -- the current stable release is 1.11.22! I strongly
suggest you update.
I used CVSNT as my local CVS server.
Big mistake. As you've discovered, CVSNT repositories are *not*
compatible with regular CVS repositories. You either need to redo the
conversion using a regular CVS server (you could use your Linux server
rather than a local server) or you need to use CVSNT on Linux.
--
Larry Jones
But Mom, frogs are our FRIENDS! -- Calvin
--
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter
http://www.crane.navy.mil/custfeedback