This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: seperating the gcc/ directory
On Tue, Apr 30, 2002 at 05:57:00PM -0400, Phil Edwards wrote:
>
> If I had free run of the GCC repository, I would copy old,v to new,v
> directly, then in a checked-out tree, "cvs remove old" with a note pointing
> to new. That's simply the form of poison I find, well, least poisonous.
That is how we do it -- note it is a good idea to do a forced commit to
new,v telling where the file was repo copied from. Or best:
cvs rm -f foo/old
cvs ci -f foo/old bar/new
noting the repo copy in a single commit -- makes tracking things easier.
We also prefix all the tags with "old_" and sometimes remove all the
branches.
This means using ``cvs co -r <TAG>'' works properly. One can easily
trace the change history (logs) w/o having to find the old files.
The only down side is that ``cvs co -D'' can give more files than really
existed on the given date. This has not proven to be a problem as the
Makefiles will still only specify the right files.
--
-- David (obrien@FreeBSD.org)