I know there is a way to export a complete CVS repository with history to git as I did so recently for an other project also on sourceforge (csvjdbc), I can't remember much more than it was an extension to git, but google for it and you will surely find it. if it was me doing the transition, I would definitely keep the cvs history: I would either construct and publish a git repository that holds the full cvs history of elks and remove the csv server. as a second choice I would keep the cvs server in its place but make it read-only. YMMV MF On Sun, 05 Feb 2012 14:22:15 -0500 Jody <jody@xxxxxxxxxxxxxxx> wrote: > I just pushed the code to Git. I don't know much about CVS and I have > always personally hated it since I got on SourceForge 11 years ago. I > just wanted to get the code in an easily reachable place as quickly > as I could, so that's what I've done. Do we need the CVS history, > moving forward? > > On 2/5/2012 2:18 PM, Kirn Gill wrote: > > > > That's one better than I had planned. I was just going to push the > > changes to CVS and call it a day. Say, did you import all the CVS > > history into git or just a checkout of the latest sources + the > > patches? > > > > -- To unsubscribe from this list: send the line "unsubscribe linux-8086" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
