# Any tricks for speeding up cvsps? 9 messages from 2008-02-08 to 2008-02-09. Participants: Paul Gardiner, Karl Hasselström, Johannes Sixt, Michael Haggerty, Johannes Schindelin, Jakub Narebski. Thread: https://gitlist.dev/t/11963 ## Paul Gardiner, 2008-02-08 09:24 Subject: Any tricks for speeding up cvsps? Message-ID: <47AC1FDC.9000502@glidos.net> URL: https://gitlist.dev/e/47AC1FDC.9000502%40glidos.net ``` Hi, I'm trying to convert a huge cvs repository. I've left cvsps running for days. First attempt, stderr filled my disc with warnings about tags that couldn't be associated with any one commit, without producing anything from stdout. I'm now redirecting stderr to /dev/null, but it still just sits there producing nothing. Is git-cvsimport infeasible for large repositories, or are there tricks I might use? P. ``` ## Karl Hasselström, 2008-02-08 09:48 Subject: Re: Any tricks for speeding up cvsps? Message-ID: <20080208094812.GA9666@diana.vm.bytemark.co.uk> URL: https://gitlist.dev/e/20080208094812.GA9666%40diana.vm.bytemark.co.uk In-Reply-To: <47AC1FDC.9000502@glidos.net> ``` On 2008-02-08 09:24:44 +0000, Paul Gardiner wrote: > I'm trying to convert a huge cvs repository. I've left cvsps running > for days. First attempt, stderr filled my disc with warnings about > tags that couldn't be associated with any one commit, without > producing anything from stdout. I'm now redirecting stderr to > /dev/null, but it still just sits there producing nothing. Is > git-cvsimport infeasible for large repositories, or are there tricks > I might use? This topic comes up on the list every once in a while; try searching the list archives. I seem to recall that for heavy imports, the Subversion CVS importer is popular. I don't know if it can give you a git repository directly, or if you'll have to go via svn. -- Karl Hasselström, kha@treskal.com www.treskal.com/kalle ``` ## Johannes Sixt, 2008-02-08 09:57 Subject: Re: Any tricks for speeding up cvsps? Message-ID: <47AC2775.5090403@viscovery.net> URL: https://gitlist.dev/e/47AC2775.5090403%40viscovery.net In-Reply-To: <47AC1FDC.9000502@glidos.net> ``` Paul Gardiner schrieb: > I'm trying to convert a huge cvs repository. I've left cvsps running for > days. First attempt, stderr filled my disc with warnings about tags that > couldn't be associated with any one commit, without producing anything > from stdout. I'm now redirecting stderr to /dev/null, but it still just > sits there producing nothing. Is git-cvsimport infeasible for large > repositories, or are there tricks I might use? I've used fast-export (not git-fast-export) to convert a CVS repository: http://repo.or.cz/w/fast-export.git It worked better than git-cvsimport because the repository was a real mess. -- Hannes ``` ## Paul Gardiner, 2008-02-08 10:11 Subject: Re: Any tricks for speeding up cvsps? Message-ID: <47AC2AC3.6020704@glidos.net> URL: https://gitlist.dev/e/47AC2AC3.6020704%40glidos.net In-Reply-To: <47AC2775.5090403@viscovery.net> ``` Johannes Sixt wrote: > I've used fast-export (not git-fast-export) to convert a CVS repository: > > http://repo.or.cz/w/fast-export.git > > It worked better than git-cvsimport because the repository was a real mess. That looks to require going either via svn or mercurial. Is that right? And if so, which did you find best? P. ``` ## Johannes Sixt, 2008-02-08 10:33 Subject: Re: Any tricks for speeding up cvsps? Message-ID: <47AC2FF6.1030103@viscovery.net> URL: https://gitlist.dev/e/47AC2FF6.1030103%40viscovery.net In-Reply-To: <47AC2AC3.6020704@glidos.net> ``` Paul Gardiner schrieb: > Johannes Sixt wrote: >> I've used fast-export (not git-fast-export) to convert a CVS repository: >> >> http://repo.or.cz/w/fast-export.git >> >> It worked better than git-cvsimport because the repository was a real >> mess. > > That looks to require going either via svn or mercurial. Is that right? > And if so, which did you find best? You are right. Because I'm utterly confused. I actually used fromcvs/togit: http://ww2.fs.ei.tum.de/~corecode/hg/fromcvs Please bear with me; I did this about a year ago. Sorry for the noise. Be warned that fromcvs/togit does not convert tags. -- Hannes ``` ## Michael Haggerty, 2008-02-08 12:02 Subject: Re: Any tricks for speeding up cvsps? Message-ID: <47AC44DB.1000002@alum.mit.edu> URL: https://gitlist.dev/e/47AC44DB.1000002%40alum.mit.edu In-Reply-To: <20080208094812.GA9666@diana.vm.bytemark.co.uk> ``` Karl Hasselström wrote: > On 2008-02-08 09:24:44 +0000, Paul Gardiner wrote: > >> I'm trying to convert a huge cvs repository. I've left cvsps running >> for days. First attempt, stderr filled my disc with warnings about >> tags that couldn't be associated with any one commit, without >> producing anything from stdout. I'm now redirecting stderr to >> /dev/null, but it still just sits there producing nothing. Is >> git-cvsimport infeasible for large repositories, or are there tricks >> I might use? > > This topic comes up on the list every once in a while; try searching > the list archives. > > I seem to recall that for heavy imports, the Subversion CVS importer > is popular. I don't know if it can give you a git repository directly, > or if you'll have to go via svn. The trunk version of cvs2svn [1] can convert directly from CVS to git, including branches and tags. Recently I wrote up better documentation [2] for using cvs2svn to convert to git. Please direct suggestions, bug reports, or offers of help to the cvs2svn mailing lists [3] or irc channel [4]. Michael Haggerty [1] http://cvs2svn.tigris.org [2] http://cvs2svn.tigris.org/cvs2git.html [3] http://cvs2svn.tigris.org/servlets/ProjectMailingListList [4] irc.freenode.net, channel #cvs2svn ``` ## Johannes Schindelin, 2008-02-08 12:23 Subject: Re: Any tricks for speeding up cvsps? Message-ID: URL: https://gitlist.dev/e/alpine.LSU.1.00.0802081222400.11591%40racer.site In-Reply-To: <47AC1FDC.9000502@glidos.net> ``` Hi, On Fri, 8 Feb 2008, Paul Gardiner wrote: > I'm trying to convert a huge cvs repository. I've left cvsps running for > days. First attempt, stderr filled my disc with warnings about tags that > couldn't be associated with any one commit, without producing anything > from stdout. I'm now redirecting stderr to /dev/null, but it still just > sits there producing nothing. Is git-cvsimport infeasible for large > repositories, or are there tricks I might use? The obvious thing is to have the CVS repository locally. And then on a ramdisk. Hth, Dscho ``` ## Jakub Narebski, 2008-02-08 12:24 Subject: Re: Any tricks for speeding up cvsps? Message-ID: URL: https://gitlist.dev/e/m3ir0zhc09.fsf%40localhost.localdomain In-Reply-To: <47AC1FDC.9000502@glidos.net> ``` Paul Gardiner writes: > I'm trying to convert a huge cvs repository. I've left cvsps running > for days. First attempt, stderr filled my disc with warnings about > tags that couldn't be associated with any one commit, without > producing anything from stdout. I'm now redirecting stderr to > /dev/null, but it still just sits there producing nothing. Is > git-cvsimport infeasible for large repositories, or are there tricks > I might use? Please check other tools to import from CVS; they are mentioned on the http://git.or.cz/gitwiki/InterfacesFrontendsAndTools wiki page ("Interaction with other Revision Control Systems" section) -- Jakub Narebski Poland ShadeHawk on #git ``` ## Paul Gardiner, 2008-02-09 08:32 Subject: Re: Any tricks for speeding up cvsps? Message-ID: <47AD6513.2040609@glidos.net> URL: https://gitlist.dev/e/47AD6513.2040609%40glidos.net In-Reply-To: <47AC2FF6.1030103@viscovery.net> ``` Johannes Sixt wrote: > Paul Gardiner schrieb: >> Johannes Sixt wrote: >>> I've used fast-export (not git-fast-export) to convert a CVS repository: >>> >>> http://repo.or.cz/w/fast-export.git >>> >>> It worked better than git-cvsimport because the repository was a real >>> mess. >> That looks to require going either via svn or mercurial. Is that right? >> And if so, which did you find best? > > You are right. Because I'm utterly confused. I actually used fromcvs/togit: > > http://ww2.fs.ei.tum.de/~corecode/hg/fromcvs > > Please bear with me; I did this about a year ago. Sorry for the noise. > > Be warned that fromcvs/togit does not convert tags. That's amazing. Less than an hour to for the initial conversion, and just minutes to progressively sync up. Thanks to everyone for all the usefull feedback I've received here. Cheers, Paul. ```