Export Git Changes to CVS

Question

I am in the process of converting a CVS repository to Git.

Currently, all developers commit any changes that they make to HEAD in CVS. Testing is done on a version of the application that is the latest from HEAD. I have an automatic script that uses git-cvsimport to bring all new commits into a Git repository. Whenever a new commit comes in I cherry pick it onto a feature branch based on the ticket number in the comment. (If there is none I yell at the developer who committed it that way, :-)) We package are production version by merging entirely with Git, although I do have a script that tags a CVS branch as well so that the developers can know what production is up to.

My end goal is to finally wean ourselves off of CVS once, and for all. However, I am not currently in the position to force the issue, so I need a workaround. I want a workflow where some users can use Git exclusively, and then merge their changes into a Git development branch, but still somehow export their changes back to CVS without to much hassle. This way I can incrementally bring developers into Git without having to make an all-or-nothing switch.

I have no admin rights, so it will be hard for me to do anything that involves setting up proxies.

Any ideas?

Answer 1

Here is a blog post that seems to give the answer:

CVS to GIT and back