This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: RFC: Moving C to its own directory
- From: "David O'Brien" <obrien at FreeBSD dot org>
- To: Steven Bosscher <s dot bosscher at student dot tudelft dot nl>
- Cc: gcc at gcc dot gnu dot org
- Date: Sun, 1 Jun 2003 13:54:00 -0700
- Subject: Re: RFC: Moving C to its own directory
- Organization: The NUXI BSD Group
- References: <20030601191930.GC5311@daikokuya.co.uk> <3EDA597E.5020002@student.tudelft.nl>
- Reply-to: obrien at FreeBSD dot org
On Sun, Jun 01, 2003 at 09:52:30PM +0200, Steven Bosscher wrote:
> >2) Create a directory fe/c/
> >3) Move c-specific and C common files, like c-lex.c, there.
...
> Can this be done without losing revision history?
You can simply create new files and make a forced commit (cvs ci -f)
noting where the files came from and one can still look at the history of
those files.
You can also do a "CVS repo copy", at the expense of twice the disk space
of the affected files. We do this all the time in the FreeBSD
repository.
> should wait until sources.redhat moves from CVS to subversions.
Is that still going to happen? AFAIK, subversion is still years away
from having the needed functionality to switch to it. It is still
missing the ability to remember which chunks have been merged and which
haven't. That's one of the bigger reasons to switch away from CVS.
--
-- David (obrien@FreeBSD.org)