This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: repository copy of FreeBSD i386 config file.
- To: obrien at freebsd dot org
- Subject: Re: repository copy of FreeBSD i386 config file.
- From: Marc Espie <espie at quatramaran dot ens dot fr>
- Date: Tue, 12 Sep 2000 23:02:42 +0200
- Cc: gcc at gcc dot gnu dot org
- Organization: Ecole Normale Superieure (quatramaran)
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.