This is the mail archive of the
mailing list for the GCC project.
Re: Moving C to its own directory (was Re: ObjC tree inlining)
- From: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- To: David O'Brien <obrien at FreeBSD dot org>
- Cc: Phil Edwards <pedwards at disaster dot jaj dot com>, Neil Booth <neil at daikokuya dot demon dot co dot uk>, Alexandre Oliva <aoliva at redhat dot com>, <gcc at gcc dot gnu dot org>
- Date: Wed, 21 Nov 2001 00:26:17 +0000 (GMT)
- Subject: Re: Moving C to its own directory (was Re: ObjC tree inlining)
On Tue, 20 Nov 2001, David O'Brien wrote:
> Why? CVS as a SCM tool stinks,
> and w/o repo copies it is an order of
> magnitude suckier. FreeBSD has *extensive* experience with repo copies.
> They work fine.
You have, for example, always avoided the problem with files both in and
out of Attic noted at:
The essential problem - if you avoid such pitfalls as this - is that it
creates a *false* history - it claims a file to have been present in some
given directory with a given name, having had given changes made to it,
when it wasn't. It also only deals with one very specific problem, that
of a whole file being moved, not of the common case of a large amount of
text from one file being moved to another.
I haven't found difficulty in using the history of documentation files
that is partly in gcc/ and partly in gcc/doc/. You could always adapt CVS
to allow direct diffing between given revisions of different files without
needing to copy ,v files or check out those specific revisions.
Joseph S. Myers