How paduartesre/cvs-to-git works
Project Type and Purpose
• This “CVS-to-GIT” project is primarily a migration/ETL (Extract, Transform, Load) pipeline: it documents the step-by-step process and the tools needed to convert a legacy CVS repository first into an SVN dump and then into a fully featured Git repository.
• There is no traditional “application” here; instead, it’s an operational workflow that ties together storage volumes, VM instances, and open-source command-line tools (cvs2svn, svnadmin, git-svn, etc.).
File Structure
• Top-level only contains LICENSE and README.md – all the “intelligence” lives in the README instructions.
• There are implicit infrastructure components:
• Backup storage volume for raw CVS dumps
• A Linux VM (or Windows VM) running Python, cvs2svn, SVN server or VisualSVN
• A final Git hosting service (GitHub/GitLab/Azure Repos)
README for Additional Insights
• The README lays out eight distinct phases:
1. Environment Prep (VM sizing, tools install)
2. Python recursion tweak for cvs2svn
3. cvs2svn → SVN-format dump
4. Import dump into SVN (VisualSVN or Linux svnadmin)
5. git-svn clone to Git (with/without authors mapping)
6. Fix tags
7. Fix branches
8. Push to remote Git hosting
• It mentions external systems/services: Samba/FTP for file transfer, MEGA cloud storage, VisualSVN, Git hosting services.