[cvsnt] Any migration caveats between CVSNT versions?

Bo Berglund bo.berglund at telia.com
Thu Oct 19 06:19:20 BST 2006

Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.

On Wed, 18 Oct 2006 18:00:23 -0400, "Paul Bennett"
<paul.w.bennett at gmail.com> wrote:

>On Wed, 18 Oct 2006 17:32:17 -0400, Bo Berglund <bo.berglund at telia.com>  
>> Yes, it is as simple concerning the actual data (RCS) files stored.
>The rest of your reply caused mine eyes to glazeth over a tiny bit. I'm a  
>sysadmin, not a CVSNT admin (nor even a cvs user).

You did not state that you know nothing about CVS in your original
post. I am assuming that people asking about migration of CVS servers
at least have a basic knowledge of the CVS system and its operation.
Unless you do then you should not attempt to "manage" a CVS server.

>However, it was full of  
>lots of useful words and phrases that ought to be findable in the  
>documentation, or at least the WWW. I actually prefer that to a "click  
>here, then here, then here" answer, so thanks!

Do I take this that you object to me sharing the experience with you
and outlining why you should do this or that?
Is it a real "thank you" or is it a "piss off" reply????

>>> Is it advisable to upgrade CVSNT on the old server before copying the
>>> data, for instance?
>> Installing or uninstalling a CVSNT server version will do exactly zero
>> on the repository itself.
>That much, at least, was (relatively) easy to understand ;-)

At least?
What was it you did not understand?


(Bo Berglund, developer in Sweden)

More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook