{"thread":{"id":"32421","subject":"Change in cvsps maintainership, abd a --fast-export option","startedAt":"2012-12-20T21:56:38Z","lastAt":"2012-12-23T19:57:24Z","messageCount":16,"participants":["Eric S. Raymond","Michael Haggerty","Heiko Voigt","Antoine Pelisse","Andreas Schwab"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"205298","messageId":"20121220215638.E54BC44119@snark.thyrsus.com","threadId":"32421","inReplyTo":null,"subject":"Change in cvsps maintainership, abd a --fast-export option","fromName":"Eric S. Raymond","fromEmail":"esr@thyrsus.com","sentAt":"2012-12-20T21:56:38Z","receivedAt":"2012-12-20T21:56:38Z","isPatch":false,"sender":{"key":"esr@thyrsus.com","avatar":"https://avatars.githubusercontent.com/u/727961?v=4"},"body":"Earlier today David Mansfield handed off to me the cvsps project. This\nis the code used as an engine for reading CVS repositories by\ngit-cvsimport.\n\nHis reason (aside from general overwork and no longer having a strong\ninterest on the code) is that I have added a --fast-export option to\ncvsps-3.0 that emits a git fast-import stream representing the CVS\nhistory.\n \nI did this so that reposurgeon could use cvsps as a front end. But I\nexpect it will be of some interest to whoever is maintaining\ngit-cvsimport. That code can now become much, *much* smaller and\nsimpler.\n\nThe new --fast-export mode solves at least one bug mentioned on the\ngit-cvsimport man page; multiple tags pointing at the same CVS changeset\nwill be passed through correctly.\n\nPossibly it fixes some other problems described there as well. \nI don't understand all the bug warnings on that page and would like to\ndiscuss them with the author, whoever that is. Possibly cvsps can be\nfurther enhanced to address these problems; I'm willing to work on that.\n-- \n\t\tEric S. Raymond\n\nTo stay young requires the unceasing cultivation of the ability to\nunlearn old falsehoods.\n\t-- Lazarus Long \n"},{"id":"205320","messageId":"50D4199C.6000002@alum.mit.edu","threadId":"32421","inReplyTo":"20121220215638.E54BC44119@snark.thyrsus.com","subject":"Re: Change in cvsps maintainership, abd a --fast-export option","fromName":"Michael Haggerty","fromEmail":"mhagger@alum.mit.edu","sentAt":"2012-12-21T08:11:08Z","receivedAt":"2012-12-21T08:11:08Z","isPatch":false,"sender":{"key":"mhagger@alum.mit.edu","avatar":"https://avatars.githubusercontent.com/u/119718?v=4"},"body":"On 12/20/2012 10:56 PM, Eric S. Raymond wrote:\n> Earlier today David Mansfield handed off to me the cvsps project. This\n> is the code used as an engine for reading CVS repositories by\n> git-cvsimport.\n> [...] I have added a --fast-export option to\n> cvsps-3.0 that emits a git fast-import stream representing the CVS\n> history.\n> [...]\n> Possibly it fixes some other problems described there as well. \n> I don't understand all the bug warnings on that page and would like to\n> discuss them with the author, whoever that is. Possibly cvsps can be\n> further enhanced to address these problems; I'm willing to work on that.\n\nIn 2009 I added tests demonstrating some of the erroneous behavior of\ngit-cvsimport. The failing tests in t9601-t9603 are concrete examples\nof the problems mentioned in the manpage.\n\nIf you haven't yet seen it, there is a writeup of the algorithm used by\ncvs2git to infer the history of a CVS repository [1]. If your goal is\nto make cvsps more robust, you might want to consider the ideas\ndescribed there.\n\nMichael\n\n[1] File doc/design-notes.txt in the cvs2svn source tree, also visible here:\n\n\nhttp://cvs2svn.tigris.org/source/browse/*checkout*/cvs2svn/trunk/doc/design-notes.txt\n\n-- \nMichael Haggerty\nmhagger@alum.mit.edu\nhttp://softwareswirl.blogspot.com/\n"},{"id":"205326","messageId":"20121221104437.GA5244@thyrsus.com","threadId":"32421","inReplyTo":"50D4199C.6000002@alum.mit.edu","subject":"Re: Change in cvsps maintainership, abd a --fast-export option","fromName":"Eric S. Raymond","fromEmail":"esr@thyrsus.com","sentAt":"2012-12-21T10:44:37Z","receivedAt":"2012-12-21T10:44:37Z","isPatch":false,"sender":{"key":"esr@thyrsus.com","avatar":"https://avatars.githubusercontent.com/u/727961?v=4"},"body":"Michael Haggerty :\n> In 2009 I added tests demonstrating some of the erroneous behavior of\n> git-cvsimport. The failing tests in t9601-t9603 are concrete examples\n> of the problems mentioned in the manpage.\n\nThanks, that will be extremely useful. One of the things I'm putting effort\ninto is building a good test suite for the tool; I may well be able to adapt\nyour tests directly.\n>\n> If you haven't yet seen it, there is a writeup of the algorithm used by\n> cvs2git to infer the history of a CVS repository [1]. If your goal is\n> to make cvsps more robust, you might want to consider the ideas\n> described there.\n\nI shall do so. Their design ideas may well be interesting, even though I\ndon't trust their code. I've seem cvs2svn drop far too many weird artifacts \nand just plain broken commits in the back history of Subversion repositories.\nI don't know if this is due to design problems, implementation bugs, or both.\n-- \n\t\tEric S. Raymond\n"},{"id":"205367","messageId":"50D4B639.9000807@alum.mit.edu","threadId":"32421","inReplyTo":"20121221104437.GA5244@thyrsus.com","subject":"Re: Change in cvsps maintainership, abd a --fast-export option","fromName":"Michael Haggerty","fromEmail":"mhagger@alum.mit.edu","sentAt":"2012-12-21T19:19:21Z","receivedAt":"2012-12-21T19:19:21Z","isPatch":false,"sender":{"key":"mhagger@alum.mit.edu","avatar":"https://avatars.githubusercontent.com/u/119718?v=4"},"body":"On 12/21/2012 11:44 AM, Eric S. Raymond wrote:\n> Michael Haggerty :\n>> If you haven't yet seen it, there is a writeup of the algorithm used by\n>> cvs2git to infer the history of a CVS repository [1]. If your goal is\n>> to make cvsps more robust, you might want to consider the ideas\n>> described there.\n> \n> I shall do so. Their design ideas may well be interesting, even though I\n> don't trust their code. I've seem cvs2svn drop far too many weird artifacts \n> and just plain broken commits in the back history of Subversion repositories.\n> I don't know if this is due to design problems, implementation bugs, or both.\n\nIf you have seen any problems with cvs2svn/cvs2git, please file bug\nreports. In the past years there have been very few valid bugs\nreported. We very often find that artifacts that users thought were\nbugs are in fact intentional workarounds required to make the contents\nof branches and tags in the target VCS agree with those in the CVS\nrepository.\n\nPerhaps your experience is with an older version of cvs2svn? If not,\nplease be specific rather than just making complaints that are too vague\nto be rebutted or fixed (whichever is appropriate). I put a *lot* of\neffort into getting cvs2svn to run correctly, and I take bug reports\nvery seriously.\n\nMichael\n(the cvs2svn maintainer)\n\n-- \nMichael Haggerty\nmhagger@alum.mit.edu\nhttp://softwareswirl.blogspot.com/\n"},{"id":"205374","messageId":"20121221214311.GA29147@thyrsus.com","threadId":"32421","inReplyTo":"50D4B639.9000807@alum.mit.edu","subject":"Re: Change in cvsps maintainership, abd a --fast-export option","fromName":"Eric S. Raymond","fromEmail":"esr@thyrsus.com","sentAt":"2012-12-21T21:43:11Z","receivedAt":"2012-12-21T21:43:11Z","isPatch":false,"sender":{"key":"esr@thyrsus.com","avatar":"https://avatars.githubusercontent.com/u/727961?v=4"},"body":"Michael Haggerty :\n> Perhaps your experience is with an older version of cvs2svn? \n\nWell, it has been at least four years since I ran it on anything.\nMaybe that counts as old. \n\nI'm willing to believe it's working better now, but I've had to deal\nwith geological strata of nastiness older versions produced in various\nSubversion repositories (cleaning up that crud was a major motivation\nfor reposurgeon) and I'm fairly sure I haven't seen the last such\nfossils. Every sufficiently old Subversion repository seems to have\nfew.\n\n> If not,\n> please be specific rather than just making complaints that are too vague\n> to be rebutted or fixed (whichever is appropriate). I put a *lot* of\n> effort into getting cvs2svn to run correctly, and I take bug reports\n> very seriously.\n\nI can't be specific now, but that may change shortly. I'm putting\ntogether a test suite for cvsps with the specific intention of\ncapturing as many odd corner cases as I can. (I just finished writing\na small Python framework for expressing interleaved CVS command\nsequences on multiple checkouts in a way that can be easily run.)\n\nIt wouldn't be difficult for me to test whether these break cvs2svn. \nYou've established that someone over there is paying attention, so\nI'll do that, I guess.\n\nI'm willing to share my test suite as well. Do you have your own zoo\nof odd cases I could test on?\n-- \n\t\tEric S. Raymond\n"},{"id":"205378","messageId":"50D4DFBD.7080708@alum.mit.edu","threadId":"32421","inReplyTo":"20121221214311.GA29147@thyrsus.com","subject":"Re: Change in cvsps maintainership, abd a --fast-export option","fromName":"Michael Haggerty","fromEmail":"mhagger@alum.mit.edu","sentAt":"2012-12-21T22:16:29Z","receivedAt":"2012-12-21T22:16:29Z","isPatch":false,"sender":{"key":"mhagger@alum.mit.edu","avatar":"https://avatars.githubusercontent.com/u/119718?v=4"},"body":"On 12/21/2012 10:43 PM, Eric S. Raymond wrote:\n> Michael Haggerty :\n>> Perhaps your experience is with an older version of cvs2svn? \n> \n> Well, it has been at least four years since I ran it on anything.\n> Maybe that counts as old. \n\ncvs2svn version 2.0 (Aug 2007) totally changed how cvs2svn deduces\nchangesets. Any results from before that are utterly irrelevant to\nmodern times.\n\nThe changes between version 2.0 and version 2.4 (Sep 2012) have done a\nlot more to improve the quality of the conversion. The state of the art\nis far beyond what it was four years ago.\n\n>> If not,\n>> please be specific rather than just making complaints that are too vague\n>> to be rebutted or fixed (whichever is appropriate). I put a *lot* of\n>> effort into getting cvs2svn to run correctly, and I take bug reports\n>> very seriously.\n> \n> I can't be specific now, but that may change shortly. I'm putting\n> together a test suite for cvsps with the specific intention of\n> capturing as many odd corner cases as I can. (I just finished writing\n> a small Python framework for expressing interleaved CVS command\n> sequences on multiple checkouts in a way that can be easily run.)\n> \n> It wouldn't be difficult for me to test whether these break cvs2svn. \n> You've established that someone over there is paying attention, so\n> I'll do that, I guess.\n\nI look forward to your results (whether positive or negative).\n\n> I'm willing to share my test suite as well. Do you have your own zoo\n> of odd cases I could test on?\n\nYes, we have a rather extensive test suite that includes lots of CVS\nperversions. See run-tests.py and the CVS repositories under test-data.\n Unfortunately, the tests mostly cover only 2svn conversions, but since\nmost of the tricky work is in the common code that infers the CVS\nhistory, cvs2git benefits from the tests too.\n\nThis discussion is getting pretty cvs2svn-specific, so we should\nprobably move it over to the cvs2svn-dev mailing list.\n\nMichael\n\n-- \nMichael Haggerty\nmhagger@alum.mit.edu\nhttp://softwareswirl.blogspot.com/\n"},{"id":"205386","messageId":"20121222034751.GA11635@book-mint","threadId":"32421","inReplyTo":"20121221104437.GA5244@thyrsus.com","subject":"Re: Re: Change in cvsps maintainership, abd a --fast-export option","fromName":"Heiko Voigt","fromEmail":"hvoigt@hvoigt.net","sentAt":"2012-12-22T03:47:51Z","receivedAt":"2012-12-22T03:47:51Z","isPatch":false,"sender":{"key":"hvoigt@hvoigt.net","avatar":"https://avatars.githubusercontent.com/u/184958?v=4"},"body":"Hi,\n\nOn Fri, Dec 21, 2012 at 05:44:37AM -0500, Eric S. Raymond wrote:\n> Michael Haggerty :\n> > In 2009 I added tests demonstrating some of the erroneous behavior of\n> > git-cvsimport. The failing tests in t9601-t9603 are concrete examples\n> > of the problems mentioned in the manpage.\n> \n> Thanks, that will be extremely useful. One of the things I'm putting effort\n> into is building a good test suite for the tool; I may well be able to adapt\n> your tests directly.\n\nBack then when I was converting some repositories to git and I also\nwrote a quick testsuite for cvsps in an attempt to fix the bugs but gave\nup. That was the point when I wrote about cvsimports limitations in the\ndocumentation.\n\nMy commits can be found here:\n\n\thttp://repo.or.cz/w/cvsps-hv.git\n\nI just quickly checked and it seems that it does not run cleanly on a\nmodern Linux anymore. If it is of interest to you I can try to get it\nrunning again.\n\nCheers Heiko\n"},{"id":"205387","messageId":"20121222062118.GA31331@thyrsus.com","threadId":"32421","inReplyTo":"20121222034751.GA11635@book-mint","subject":"Re: Re: Change in cvsps maintainership, abd a --fast-export option","fromName":"Eric S. Raymond","fromEmail":"esr@thyrsus.com","sentAt":"2012-12-22T06:21:18Z","receivedAt":"2012-12-22T06:21:18Z","isPatch":false,"sender":{"key":"esr@thyrsus.com","avatar":"https://avatars.githubusercontent.com/u/727961?v=4"},"body":"Heiko Voigt :\n> Back then when I was converting some repositories to git and I also\n> wrote a quick testsuite for cvsps in an attempt to fix the bugs but gave\n> up. That was the point when I wrote about cvsimports limitations in the\n> documentation.\n> \n> My commits can be found here:\n> \n> \thttp://repo.or.cz/w/cvsps-hv.git\n> \n> I just quickly checked and it seems that it does not run cleanly on a\n> modern Linux anymore. If it is of interest to you I can try to get it\n> running again.\n\nThat would be helpful. Please give it some effort.\n\nI'm going to work on merging the cvsps patches Yann Dirson has been \naccumulating.\n-- \n\t\tEric S. Raymond\n"},{"id":"205409","messageId":"20121222130452.GB13549@book-mint","threadId":"32421","inReplyTo":"20121222062118.GA31331@thyrsus.com","subject":"Re: Re: Re: Change in cvsps maintainership, abd a --fast-export option","fromName":"Heiko Voigt","fromEmail":"hvoigt@hvoigt.net","sentAt":"2012-12-22T13:04:52Z","receivedAt":"2012-12-22T13:04:52Z","isPatch":false,"sender":{"key":"hvoigt@hvoigt.net","avatar":"https://avatars.githubusercontent.com/u/184958?v=4"},"body":"Hi,\n\nOn Sat, Dec 22, 2012 at 01:21:18AM -0500, Eric S. Raymond wrote:\n> Heiko Voigt :\n> > Back then when I was converting some repositories to git and I also\n> > wrote a quick testsuite for cvsps in an attempt to fix the bugs but gave\n> > up. That was the point when I wrote about cvsimports limitations in the\n> > documentation.\n> > \n> > My commits can be found here:\n> > \n> > \thttp://repo.or.cz/w/cvsps-hv.git\n> > \n> > I just quickly checked and it seems that it does not run cleanly on a\n> > modern Linux anymore. If it is of interest to you I can try to get it\n> > running again.\n> \n> That would be helpful. Please give it some effort.\n\nHere you go. I have pushed my changes on the master branch there.\n\nYou should now be able to run my tests with\n\n\tmake test\n\nfrom the root directory of the repository. The expected and actual\noutput can be found in the t[0-9]{4}... directories underneath t/.\n\nCheers Heiko\n"},{"id":"205410","messageId":"20121222140453.GB375@thyrsus.com","threadId":"32421","inReplyTo":"20121222034751.GA11635@book-mint","subject":"Re: Re: Change in cvsps maintainership, abd a --fast-export option","fromName":"Eric S. Raymond","fromEmail":"esr@thyrsus.com","sentAt":"2012-12-22T14:04:53Z","receivedAt":"2012-12-22T14:04:53Z","isPatch":false,"sender":{"key":"esr@thyrsus.com","avatar":"https://avatars.githubusercontent.com/u/727961?v=4"},"body":"Heiko Voigt :\n> My commits can be found here:\n> \n> \thttp://repo.or.cz/w/cvsps-hv.git\n> \n> I just quickly checked and it seems that it does not run cleanly on a\n> modern Linux anymore. If it is of interest to you I can try to get it\n> running again.\n\nesr@snark:~/WWW/cvsps/fixrepos$ git clone http://repo.or.cz/w/cvsps-hv.git\nCloning into 'cvsps-hv'...\nfatal: http://repo.or.cz/w/cvsps-hv.git/info/refs not valid: is this a git repository?\n\nDoesn't seem to be a good day for cloning - I can't get Yann's repo either,\nsomething about HEAD pointing to an invalid reference.\n-- \n\t\tEric S. Raymond\n"},{"id":"205413","messageId":"CALWbr2zZFq_9qa+pTx3nYn+KFv61LrSMcNM4N1Xs5cmnr8teXg@mail.gmail.com","threadId":"32421","inReplyTo":"20121222140453.GB375@thyrsus.com","subject":"Re: Re: Change in cvsps maintainership, abd a --fast-export option","fromName":"Antoine Pelisse","fromEmail":"apelisse@gmail.com","sentAt":"2012-12-22T14:10:02Z","receivedAt":"2012-12-22T14:10:02Z","isPatch":false,"sender":{"key":"apelisse@gmail.com","avatar":"https://avatars.githubusercontent.com/u/1929644?v=4"},"body":"> esr@snark:~/WWW/cvsps/fixrepos$ git clone http://repo.or.cz/w/cvsps-hv.git\n> Cloning into 'cvsps-hv'...\n> fatal: http://repo.or.cz/w/cvsps-hv.git/info/refs not valid: is this a git repository?\n\nI guess 'w' means write, and you don't have write access. You should use\n\n http://repo.or.cz/r/cvsps-hv.git\n\ninstead. It works for me.\n"},{"id":"205411","messageId":"20121222141519.GA2080@thyrsus.com","threadId":"32421","inReplyTo":"20121222130452.GB13549@book-mint","subject":"Re: Re: Re: Change in cvsps maintainership, abd a --fast-export option","fromName":"Eric S. Raymond","fromEmail":"esr@thyrsus.com","sentAt":"2012-12-22T14:15:19Z","receivedAt":"2012-12-22T14:15:19Z","isPatch":false,"sender":{"key":"esr@thyrsus.com","avatar":"https://avatars.githubusercontent.com/u/727961?v=4"},"body":"Heiko Voigt :\n> Hi,\n> \n> On Sat, Dec 22, 2012 at 01:21:18AM -0500, Eric S. Raymond wrote:\n> > Heiko Voigt :\n> > > Back then when I was converting some repositories to git and I also\n> > > wrote a quick testsuite for cvsps in an attempt to fix the bugs but gave\n> > > up. That was the point when I wrote about cvsimports limitations in the\n> > > documentation.\n> > > \n> > > My commits can be found here:\n> > > \n> > > \thttp://repo.or.cz/w/cvsps-hv.git\n> > > \n> > > I just quickly checked and it seems that it does not run cleanly on a\n> > > modern Linux anymore. If it is of interest to you I can try to get it\n> > > running again.\n> > \n> > That would be helpful. Please give it some effort.\n> \n> Here you go. I have pushed my changes on the master branch there.\n> \n> You should now be able to run my tests with\n> \n> \tmake test\n> \n> from the root directory of the repository. The expected and actual\n> output can be found in the t[0-9]{4}... directories underneath t/.\n> \n> Cheers Heiko\n\nsr@snark:~/WWW/cvsps/fixrepos$ git clone http://repo.or.cz/w/cvsps-hv.git\nCloning into 'cvsps-hv'...\nfatal: http://repo.or.cz/w/cvsps-hv.git/info/refs not valid: is this a git repository?\n\n-- \n\t\tEric S. Raymond\n"},{"id":"205412","messageId":"20121222141710.GB2080@thyrsus.com","threadId":"32421","inReplyTo":"CALWbr2zZFq_9qa+pTx3nYn+KFv61LrSMcNM4N1Xs5cmnr8teXg@mail.gmail.com","subject":"Re: Re: Change in cvsps maintainership, abd a --fast-export option","fromName":"Eric S. Raymond","fromEmail":"esr@thyrsus.com","sentAt":"2012-12-22T14:17:10Z","receivedAt":"2012-12-22T14:17:10Z","isPatch":false,"sender":{"key":"esr@thyrsus.com","avatar":"https://avatars.githubusercontent.com/u/727961?v=4"},"body":"Antoine Pelisse :\n> > esr@snark:~/WWW/cvsps/fixrepos$ git clone http://repo.or.cz/w/cvsps-hv.git\n> > Cloning into 'cvsps-hv'...\n> > fatal: http://repo.or.cz/w/cvsps-hv.git/info/refs not valid: is this a git repository?\n> \n> I guess 'w' means write, and you don't have write access. You should use\n> \n> http://repo.or.cz/r/cvsps-hv.git\n> \n> instead. It works for me.\n\nOK, that got it. Looking at the tests now.\n-- \n\t\tEric S. Raymond\n"},{"id":"205414","messageId":"m2vcbuqia9.fsf@igel.home","threadId":"32421","inReplyTo":"20121222140453.GB375@thyrsus.com","subject":"Re: Change in cvsps maintainership, abd a --fast-export option","fromName":"Andreas Schwab","fromEmail":"schwab@linux-m68k.org","sentAt":"2012-12-22T14:21:34Z","receivedAt":"2012-12-22T14:21:34Z","isPatch":false,"sender":{"key":"schwab@linux-m68k.org","avatar":"https://avatars.githubusercontent.com/u/2175493?v=4"},"body":"\"Eric S. Raymond\" writes:\n\n> esr@snark:~/WWW/cvsps/fixrepos$ git clone http://repo.or.cz/w/cvsps-hv.git\n\n>From :\n\nURL git://repo.or.cz/cvsps-hv.git\n http://repo.or.cz/r/cvsps-hv.git\n\nAndreas.\n\n-- \nAndreas Schwab, schwab@linux-m68k.org\nGPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5\n\"And now for something completely different.\"\n"},{"id":"205417","messageId":"m2r4miqciy.fsf@igel.home","threadId":"32421","inReplyTo":"CALWbr2zZFq_9qa+pTx3nYn+KFv61LrSMcNM4N1Xs5cmnr8teXg@mail.gmail.com","subject":"Re: Change in cvsps maintainership, abd a --fast-export option","fromName":"Andreas Schwab","fromEmail":"schwab@linux-m68k.org","sentAt":"2012-12-22T16:25:57Z","receivedAt":"2012-12-22T16:25:57Z","isPatch":false,"sender":{"key":"schwab@linux-m68k.org","avatar":"https://avatars.githubusercontent.com/u/2175493?v=4"},"body":"Antoine Pelisse writes:\n\n> I guess 'w' means write\n\nNo, 'w' mean gitweb.\n\nAndreas.\n\n-- \nAndreas Schwab, schwab@linux-m68k.org\nGPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5\n\"And now for something completely different.\"\n"},{"id":"205451","messageId":"20121223195724.GA29354@book-mint","threadId":"32421","inReplyTo":"20121222141519.GA2080@thyrsus.com","subject":"Re: Re: Re: Re: Change in cvsps maintainership, abd a --fast-export option","fromName":"Heiko Voigt","fromEmail":"hvoigt@hvoigt.net","sentAt":"2012-12-23T19:57:24Z","receivedAt":"2012-12-23T19:57:24Z","isPatch":false,"sender":{"key":"hvoigt@hvoigt.net","avatar":"https://avatars.githubusercontent.com/u/184958?v=4"},"body":"On Sat, Dec 22, 2012 at 09:15:19AM -0500, Eric S. Raymond wrote:\n> sr@snark:~/WWW/cvsps/fixrepos$ git clone http://repo.or.cz/w/cvsps-hv.git\n> Cloning into 'cvsps-hv'...\n> fatal: http://repo.or.cz/w/cvsps-hv.git/info/refs not valid: is this a git repository?\n\nThat link refers to the webpage of the repository. The clone url is found on\nthat page. Use this address for cloning:\n\n\tgit://repo.or.cz/cvsps-hv.git\n\nCheers Heiko\n"}]}