681
edits
Changes
Jump to navigation
Jump to search
Line 134:
Line 134: − + + + + + + + + + + + + + + + + + + + + + + + +
→Bringing across all the CVS history as well...
It includes a "cvsconvert" script which runs cvs-fast-convert and writes to a git repo.
It includes a "cvsconvert" script which runs cvs-fast-convert and writes to a git repo.
HOWEVER it needs access to the CVS files, not just the cvs client!
HOWEVER it needs access to the CVS files, not just the cvs client!<syntaxhighlight>
[brianr@rockysmebuild cvs-fast-export]$ more cvsconvert
#!/usr/bin/env python3
"""
cvsconvert - convert a CVS repo and check against the original
Convert, and check the tree content of a gitspace conversion against
the CVS. The tip state of every branch, and every tag, is checked.
Will produce spurious errors if any CVS branch name had to be sanitized.
</syntaxhighlight>cvssync (part of the cvs package) is the way to go.
See here: https://stackoverflow.com/questions/28693868/migration-from-cvs-to-git
This worked:
cvssync brianr@shell.koozali.org:/cvs/smecontribs/rpms smeserver-ddclient
it creates a directory "smeserver-ddclient" of the CVS files.
and "find . | cvs-fast-export | git fast-import" also did something, although I am not sure it was quite what I expected!!
TBC (WIP)