cvs init on pre-existing old repository ok?

[Bulgrien, Kevin]

The original question was:

A user did a cvs init on an existing repository.  Is this generally safe,
or might it be advisable to go back and check for differences against a
backup?

CVS version is 1.11.17

http://lists.gnu.org/archive/html/info-cvs/2004-05/msg00050.html

presumably contains an applicable answer:

> The 'cvs init' should only add files that are not already present but
> are needed by cvs."

 ...

> The 'cvs init' function should not do anything bad to your files unless
> you happen to have files in the $CVSROOT/CVSROOT that do not match the
> top-of-tree version in their corresponding ,v file in the checkoutlist.
>
> It is probably a good idea to create a test copy of the CVSROOT
> directory into another repository and run the 'cvs init' command to see
> what it does to your test setup before you do the real thing.
>
>        Good luck,
>        -- Mark

It does appear that one needs to check a backup in order to be sure since
the full context of the cvs init operation is not known.

--- 
Kevin R. Bulgrien
Product Engineer

General Dynamics C4 Systems                   http://www.tripointglobal.com/
VertexRSI
1915 Harrison Road                                    Tel: 903-295-1480 x288
Longview, TX 75604-5438                               Fax: 903-295-1479