Git to CVS: how do I _regress_?

Question

Because I'm totally insane (well, there are better reasons but I'm not allowed to talk about them), what's the best approach to port a Git repo to CVS? I haven't used any Git-specific features that I can think of that would hinder the operation, and I know how the authors map.

There are thousands of hits everywhere for CVS->Git. I want to go the other way.

So, it seems is everyone. I'd prefer to stick with Git too. – Jashank Jeremy Apr 27 '11 at 00:48 — Jashank Jeremy, Apr 27 '11 at 00:48

score 1 · Answer 1 · edited May 23 '17 at 12:03

1

This question and the accepted answer has a section on exporting changes to CVS. Maybe you can create an empty CVS repository and then export your current HEAD to that?

I feel for you though...

edited May 23 '17 at 12:03

Community

1
1

answered Apr 26 '11 at 12:12

Noufal Ibrahim

71,383
13
135
169

`cvsexportcommit` looks like it might be of use here. I'll have a play with it, and see what I get. – Jashank Jeremy Apr 27 '11 at 00:53

score 1 · Answer 2 · answered Apr 26 '11 at 12:37

1

If you by any chance had an option to live with mixed setup, where the server is still git, there is git cvsserver command (part of git, though various distributions package it separately, because few people need it). That would allow you to keep using git for some work and still access it with CVS where you are stuck with that.

answered Apr 26 '11 at 12:37

Jan Hudec

73,652
13
125
172

I'd also like to stay with Git, but we have to migrate to CVS, unfortunately. It's a shame that there's no obvious way to replicate a CVS repository from an existing CVS server, otherwise I'd use `git-cvsserver` and copy from it. – Jashank Jeremy Apr 27 '11 at 00:51

Git to CVS: how do I _regress_?

2 Answers2