Projects with CVS *and* Subversion repositories

Erik Huelsmann ehuels at gmail.com
Sun Apr 5 17:47:44 UTC 2015


Dear all,


In preparation of migrating away from CVS, I've found a number of projects
which have a non-empty CVS repository as well as a non-empty Subversion
repository. To notify these projects, I've sent the mail below. However,
some projects have not received this mail, because the member's e-mail
addresses in the .forward file can't be reached.

The projects which haven't received the notification are:

plain-odbc : raverkamp at common-lisp.net
cl-libtai: lvecsey at common-lisp.net

If anybody knows how to reach these users, please forward this e-mail. If
no reaction pops up (either by the project owner or someone who feels the
need), the default action as mentioned in the mail will kick in (i.e. we'll
assume the CVS repo is a remnant of a CVS->Subversion migration).


Kindest regards,


Erik.


-----------------------------------------------------------

Dear members of the <project> project,


As part of the migration of common-lisp.net to a more coherent and
easier to support structure, it was discovered that your project
has both a non-empty CVS repository as well as a non-empty Subversion
repository.

Because support for CVS repositories will be removed from the system
in the months to come, we'd like to know if your CVS repository is a
duplicate of the CVS repository or old remnant, even.

We're currently assuming you *don't* need your CVS repository to be
migrated anywhere (it's a duplicate or old remnant). We'll remove it.

**** If this assumption is incorrect, please respond to this e-mail
     by 2015-04-12, telling us what you want to happen to your /CVS/
     repository ****

Your options are
 1. Migrate to Git
 2. Migrate to Subversion


Thank you for your cooperation!


Kindest regards,



Erik Hulsmann
common-lisp.net admins
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/clo-devel/attachments/20150405/ab8d1109/attachment.html>


More information about the clo-devel mailing list