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 firstname.lastname@example.org.
The way that I know that keeps the old history but gives history for the new file too is as follows. 1. Copy 'oldname,v' to 'newname,v' in the repository (note copy, not move) 2. Cvs remove 'oldname' using a client. Copying the original file in the repository means that it remains available under its old name, keeping its history there. Helpfully, Maybe, Richard. > -----Original Message----- > From: cvsnt-bounces at cvsnt.org > [mailto:cvsnt-bounces at cvsnt.org] On Behalf Of Gerhard Fiedler > Sent: 05 September 2008 12:31 > To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook > Subject: Re: [cvsnt] Unable to access a renamed filed > > Arthur Barrett wrote: > > >> Since I have only renamed one file, is it possible of hack the > >> repository to permanently change the file name? > > > > Yes - this is the 'old' way. If this is the only renamed file just > > delete the .directory_history,v before renaming the ,v file. > > Actually, this is one of the 'old' ways; the other is remove > old/add new. > The disadvantage of renaming in the repo is that checkouts > with tags before > the rename still get the new file name, which may break a > build. (If you > renamed a file that is referenced in other files by name, for > example a .c > file that's referenced in a makefile, a .h file that's > included in a .c > file, etc.) > > Gerhard > _______________________________________________ > cvsnt mailing list > cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook > http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs >