From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marc Espie To: obrien@freebsd.org Cc: gcc@gcc.gnu.org Subject: Re: repository copy of FreeBSD i386 config file. Date: Tue, 12 Sep 2000 14:03:00 -0000 Message-id: <200009122102.XAA11873@quatramaran.ens.fr> References: <20000904135248.A46304@dragon.nuxi.com> X-SW-Source: 2000-09/msg00232.html You definitely don't want to move ,v files around on any project where you wish to keep history and be able to check out old versions and have them work. The only leeway that cvs leaves you, in my experience, is that you can duplicate a ,v file, to keep a better sense of history of a file (this makes it appear as if the file was always there in the old checkouts). You still have to make sure a new version of the new file is checked in, possibly forcibly if you just want to move stuff around. You'd better have very good reasons for such a hack (such as a 300 revisions long history), otherwise, the classical cp old new cvs rm -f old cvs add new cvs commit old new works just fine.