https://github.com/mhagger/cvs2svn
Migrate CVS repositories to Subversion or Git. This site supersedes the old tigris.org site, which has shut down.
https://github.com/mhagger/cvs2svn
Last synced: 4 months ago
JSON representation
Migrate CVS repositories to Subversion or Git. This site supersedes the old tigris.org site, which has shut down.
- Host: GitHub
- URL: https://github.com/mhagger/cvs2svn
- Owner: mhagger
- License: other
- Created: 2011-03-23T10:32:15.000Z (almost 15 years ago)
- Default Branch: master
- Last Pushed: 2024-05-27T11:32:06.000Z (over 1 year ago)
- Last Synced: 2025-07-02T10:51:36.792Z (6 months ago)
- Language: Python
- Homepage:
- Size: 10.8 MB
- Stars: 85
- Watchers: 10
- Forks: 44
- Open Issues: 9
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGES.md
- License: COPYING
Awesome Lists containing this project
README
# cvs2svn - CVS to Subversion Repository Converter
:warning: cvs2svn is now in maintenance mode and is not actively being
developed. :warning:
cvs2svn is a tool for migrating a CVS repository to Subversion, git,
or Bazaar. The main design goals are robustness and 100% data
preservation. cvs2svn can convert just about any CVS repository we've
ever seen. For example, it has been used to convert gcc, FreeBSD, KDE,
GNOME, PostgreSQL…
cvs2svn infers what happened in the history of your CVS repository and
replicates that history as accurately as possible in the target SCM.
All revisions, branches, tags, log messages, author names, and commit
dates are converted. cvs2svn deduces what CVS modifications were made
at the same time, and outputs these modifications grouped together as
changesets in the target SCM. cvs2svn also deals with many CVS quirks
and is highly configurable. See the comprehensive [feature
list](features.md).
You can get the latest releases [from the GitHub releases
page](https://github.com/mhagger/cvs2svn/releases). Please read [the
documentation](cvs2svn.md) and [the FAQ](faq.md) carefully before
using cvs2svn.
For general use, the most recent released version of cvs2svn is
usually the best choice. However, if you want to use the newest
cvs2svn features or if you're debugging or patching cvs2svn, you might
want to use the master version (which is usually quite stable). To do
so, use Git to clone the repository, and run it straight from the
working copy.
This repository contains a `Dockerfile` that can be used to create a
docker image in which cvs2svn can be run. (It has some dependencies
that are no longer easily installable, so this is probably the easiest
way to run cvs2svn.)