git-cvs

In order to import a revision of a CVS module, I am using: /usr/lib/git-core/git-cvsimport -a -i -p r,revisionname -k -v -d :pserver:user@xxx.com:2401/srv/cvs/rootname modulename It works for a while and then I get something like cvsps got an error. How do I determine what the cvsps error is? reza Gave up on this approach and have used cvs2git . The cvs2git is a tool that can be used to migrate CVS repositories to newer version control tools, including git. Sample usage: cvs2git \ --blobfile=cvs2git-tmp/git-blob.dat \ --dumpfile=cvs2git-tmp/git-dump.dat \ --username=cvs2git \ /path/to/cvs/repo

There is a central repository in CVS, and I would like to use it with Git locally, and then send my changes back to CVS. What can I accomplish that on a daily basis? The tasks I would like to accomplish are: importing branches, getting history in GIT-like format, and exporting back my changes/commits to the centralized server BTW, I have also looked at Best practices for using git with CVS . But It didn't work and I couldn't figure out what I missed or did wrong. gpoo What I have done in the past is: Import the CVS repository Using: $ git cvsimport -C target-cvs -r cvs -k -vA authors-file.txt

What are your best practices and tips for using git to interface with a CVS repository? Brian Phillips I wrote up an answer to a similar question here . This works suprisingly well when you're forced to continue to push changes into a central CVS repository. Paul I've only worked with Git-CVS interactions to demo Git for a friend, but it was very straightforward. You need to install a current copy of cvsps . Git cvsimport uses this to access CVS history. We found that, for a large project, inital set-up was much faster by taking a full copy of the CVS repo onto your computer, and doing the git