{"thread":{"id":"15890","subject":"How many users of parsecvs are there?","startedAt":"2008-10-14T10:10:00Z","lastAt":"2008-10-14T16:51:12Z","messageCount":3,"participants":["Alex Bennee","Johannes Schindelin","Mike Ralphson"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"92997","messageId":"b2cdc9f30810140310l647eb2fbld3f6a1c608d029a@mail.gmail.com","threadId":"15890","inReplyTo":null,"subject":"How many users of parsecvs are there?","fromName":"Alex Bennee","fromEmail":"kernel-hacker@bennee.com","sentAt":"2008-10-14T10:10:00Z","receivedAt":"2008-10-14T10:10:00Z","isPatch":false,"sender":{"key":"kernel-hacker@bennee.com","avatar":null},"body":"I'm wondering how many people are there still using parsecvs to to\ntrack a live CVS tree?\n\nI've been using it for a while at work to track a rather monster CVS\nrepository. The main reasons are:\n\n1. It's the fastest import I've come across so far. Given the size of\nthe CVS repo other solutions took far too long to do the conversion\n2. It's simple to configure (if you can call \"find\" configuring),\nassuming you have access to the CVS repo proper\n3. It reliably regenerates the repository so you can run the entire\nconversion from scratch the next day and hapily pull into working\nrepos (I assume if I got tother working they should exhibit this\nproperty).\n\nHowever I have come across a few problems. One of which involves files\nnot getting put into branches which I've managed hack a band-aid\nsolution for that involves ignoring date discrepancies. However having\nmailed keith he made it clear he doesn't use it any more having\nconverted his stuff so it's currently not being actively maintained.\n\nSo the question really is are there people out there still using it?\nIf not I'll hang up my code exploring boots and have another go at\nwhatever is considered the best in class iterative CVS to GIT gateway.\nIf it's still a useful tool for other people as well I'm happy to\ndelve deeper into the code and seeing if any of the crinkles can be\nironed out.\n\nIt's interesting to note from the Git Users Survey 2008 that CVS is\nstill the second most used legacy version control system. One could\ndraw the conclusion that having a well supported bullet proof\nincremental CVS import mechanism as part of git should still be a\nfairly important goal. There are a lot (too many?)  out of tree\nsolutions out there which makes approaching the task somewhat daunting\nwhen first coming to git.\n\n-- \nAlex, homepage: http://www.bennee.com/~alex/\n"},{"id":"93015","messageId":"alpine.DEB.1.00.0810141820110.22125@pacific.mpi-cbg.de.mpi-cbg.de","threadId":"15890","inReplyTo":"b2cdc9f30810140310l647eb2fbld3f6a1c608d029a@mail.gmail.com","subject":"Re: How many users of parsecvs are there?","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2008-10-14T16:21:01Z","receivedAt":"2008-10-14T16:21:01Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Tue, 14 Oct 2008, Alex Bennee wrote:\n\n> I'm wondering how many people are there still using parsecvs to to track \n> a live CVS tree?\n\nI used it in conjunction with clonecvs at some stage, but did not need to \nuse parsecvs in the end, so I stayed with cvsimport.\n\nCiao,\nDscho\n"},{"id":"93017","messageId":"e2b179460810140951v3bcfc951xc211b70e71ec198e@mail.gmail.com","threadId":"15890","inReplyTo":"alpine.DEB.1.00.0810141820110.22125@pacific.mpi-cbg.de.mpi-cbg.de","subject":"Re: How many users of parsecvs are there?","fromName":"Mike Ralphson","fromEmail":"mike.ralphson@gmail.com","sentAt":"2008-10-14T16:51:12Z","receivedAt":"2008-10-14T16:51:12Z","isPatch":false,"sender":{"key":"mike.ralphson@gmail.com","avatar":"https://avatars.githubusercontent.com/u/21603?v=4"},"body":"On Tue, 14 Oct 2008, Alex Bennee wrote:\n>\n> I'm wondering how many people are there still using parsecvs to to track\n> a live CVS tree?\n\nI used it to import some problematic historical CVS projects into git.\nIt coped with the (probably) broken history better than cvsps did at\nthe time, though I had to hack it to ignore some non-standard\ndirectives in the ,v files (deltatype, permissions etc).\n\nAt the time that was a one-off exercise, but the project which\nreplaced that project has now itself been cancelled and it is just\npossible the original will be revived (!)\n\nHopefully though, the egit project would now be sufficient for us to\ngo forward based on the converted history in git and leave CVS behind.\n\nMike\n"}]}