# git cvsimport and deleted files 4 messages from 2008-07-20 to 2008-07-20. Participants: Paul Mackerras, Johannes Schindelin, Lars Noschinski. Thread: https://gitlist.dev/t/14546 ## Paul Mackerras, 2008-07-20 12:09 Subject: git cvsimport and deleted files Message-ID: <18563.10979.379533.580413@cargo.ozlabs.ibm.com> URL: https://gitlist.dev/e/18563.10979.379533.580413%40cargo.ozlabs.ibm.com ``` I just tried importing the CVS repository for a long-running project (ppp) into git using git cvsimport. It looks like git cvsimport doesn't notice when files have been deleted, so files that used to be present and were subsequently deleted are present in the git tree for the most recent commit. Is this a known problem? Is it a limitation of cvsps? I know that cvs doesn't represent deletions explicitly anywhere, so I guess it's not surprising, but it is a bit annoying. Paul. ``` ## Johannes Schindelin, 2008-07-20 12:49 Subject: Re: git cvsimport and deleted files Message-ID: URL: https://gitlist.dev/e/alpine.DEB.1.00.0807201448020.3305%40eeepc-johanness In-Reply-To: <18563.10979.379533.580413@cargo.ozlabs.ibm.com> ``` Hi, On Sun, 20 Jul 2008, Paul Mackerras wrote: > I just tried importing the CVS repository for a long-running project > (ppp) into git using git cvsimport. It looks like git cvsimport > doesn't notice when files have been deleted, so files that used to be > present and were subsequently deleted are present in the git tree for > the most recent commit. I never had that problem. See http://repo.or.cz/w/libvncserver.git?a=commit;h=8dead0759febaa7176507e1bde13ebd9d2a30720 for a commit that was imported with cvsimport. So your issue must lie somewhere else. BTW do you have the repository locally? Then you should import with cvs2svn or parsecvs instead. These programs are both faster and more accurate than cvsimport. And AFAIK you can use cvsimport on the generated repositories to update them incrementally. Ciao, Dscho ``` ## Lars Noschinski, 2008-07-20 18:04 Subject: Re: git cvsimport and deleted files Message-ID: <20080720180432.GA30285@lars.home.noschinski.de> URL: https://gitlist.dev/e/20080720180432.GA30285%40lars.home.noschinski.de In-Reply-To: ``` * Johannes Schindelin [08-07-20 14:49]: >> I just tried importing the CVS repository for a long-running project >> (ppp) into git using git cvsimport. It looks like git cvsimport >> doesn't notice when files have been deleted, so files that used to be >> present and were subsequently deleted are present in the git tree for >> the most recent commit. > >I never had that problem. See >http://repo.or.cz/w/libvncserver.git?a=commit;h=8dead0759febaa7176507e1bde13ebd9d2a30720 >for a commit that was imported with cvsimport. > >So your issue must lie somewhere else. I encountered such an issue some time ago in incremental mode, when another person did some cvs branch stuff. The error persisted even as I did a clean checkout, but disappeared, after I deleted all the cvsps cache files. I failed to report the error, because I had not much time for debugging at that time and I would not have been able to publish the repository. That's when I switched to fromcvs, which seems to work reliably so far (and much faster), but requires a local repository. ``` ## Lars Noschinski, 2008-07-20 18:05 Subject: Re: git cvsimport and deleted files Message-ID: <20080720180513.GB30285@lars.home.noschinski.de> URL: https://gitlist.dev/e/20080720180513.GB30285%40lars.home.noschinski.de In-Reply-To: ``` * Johannes Schindelin [08-07-20 14:49]: >>I just tried importing the CVS repository for a long-running project >>(ppp) into git using git cvsimport. It looks like git cvsimport >>doesn't notice when files have been deleted, so files that used to be >>present and were subsequently deleted are present in the git tree for >>the most recent commit. > >I never had that problem. See >http://repo.or.cz/w/libvncserver.git?a=commit;h=8dead0759febaa7176507e1bde13ebd9d2a30720 >for a commit that was imported with cvsimport. > >So your issue must lie somewhere else. I encountered such an issue some time ago in incremental mode, when another person did some cvs branch stuff. The error persisted even as I did a clean checkout, but disappeared, after I deleted all the cvsps cache files. I failed to report the error, because I had not much time for debugging at that time and I would not have been able to publish the repository. That's when I switched to fromcvs, which seems to work reliably so far (and much faster), but requires a local repository. ```