Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
>-----Original Message----- >From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf Of Bo Berglund >Sent: Tuesday, August 17, 2004 3:35 PM >To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook >Subject: Re: [cvsnt] Re: deleting a module from repository > >On Tue, 17 Aug 2004 15:29:25 -0600, "Siegfried Heintze" ><siegfried at heintze.com> wrote: > >> >>Can you elaborate on your emphasis? Why might we be so reluctant to delete >>directories in the repository? >> > >The CVS repository is a store that holds the complete history of all >source files of all of the controlled projects. As such it is supposed >to be able to bring back exactly any demanded old file situation (by >the use of tags) of any project and every single once existing >revision of any file. >In this context it is really a bad idea to go into the repository >(which resides in the server) and delete anything forcibly using >operating system tools. What this does is permanently destroy any hope >of being able to restore old files in the future. This is why Glen put >the emphasis on the delete suggestion. > >On the other hand if you are experimenting in a test repository and >know what you are doing, then you can of course remove modules >(=directories) from the server as much as you like. > >When you use the cvs remove command all it does is that it mark the >file in the repository as non-existing for future work, but it is >still there for retrieval of old tagged snapshots. The removal is >information that gets stored into the RCS file in the repository as >information. >And since CVS does not deal with folders in a source control sense >these cannot be removed at all, once created they stay there. So considering my scenario: I have a repository and directory under version control. If my second import command is bogus, I can recover by deleting it from the repository and adding it to the repository a second time correctly. > >Hope this helps, > >/Bo >(Bo Berglund, developer in Sweden)