- Original Message -
From: Denniston, Todd A CIV NAVSURFWARCENDIV Crane, Code JSXN
[EMAIL PROTECTED]
To: Vinod Damaraju [EMAIL PROTECTED]
Cc: info-cvs@nongnu.org
Sent: Tuesday, July 15, 2008 9:46 AM
Subject: Re: CVSNT versus CVS
Vinod Damaraju wrote, On 07/13/2008 07:40 PM:
Larry,
Thank
Vinod,
If I use the
remote CVS server, a signifcant functionality of the
conversion tool would
not work.
In that case it appears as though the 'conversion tool' you are using
requires CVSNT - that means it requires CVSNT. If you are not using
CVSNT then you need to find another
Message - From: Larry Jones
[EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: info-cvs@nongnu.org
Sent: Wednesday, July 09, 2008 6:31 PM
Subject: Re: CVSNT versus CVS
[EMAIL PROTECTED] writes:
CVS server was on Linux and was CVS 1.11.2.
That is *ancient* -- the current stable release is 1.11.22
: Re: CVSNT versus CVS
[EMAIL PROTECTED] 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
I have been involved in converting our source code repository in Visual
Source Safe (VSS) to CVS and would like to share my experiences. In the
process, I did find one difference in the format of ,v files about which I
have a question. Below is a summary of what I did and I would appreciate
[EMAIL PROTECTED] 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
Vinod Damaraju,
I have been involved in converting our source
code repository in Visual Source Safe (VSS)
to CVS snip
Note1: it is not possible to convert from any SCM to any other - you can
extract the information from one SCM tool and import it into another,
but since each SCM tool has
