This is the mail archive of the
gcc@gcc.gnu.org
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: Phil Edwards <pedwards at disaster dot jaj dot com>
- Cc: 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: Mon, 19 Nov 2001 17:38:43 +0000 (GMT)
- Subject: Re: Moving C to its own directory (was Re: ObjC tree inlining)
On Mon, 19 Nov 2001, Phil Edwards wrote:
> The usual objection to this is that it makes CVS history browsing more
> difficult,e.g., the problems discussed in
>
> http://www.cvshome.org/docs/manual/cvs_7.html#SEC66
>
> No matter which of the two or three methods of moving files we use, at
> least one CVS operation will be much harder.
It's established that we only ever use cvs add / cvs remove, and don't do
anything directly in the repository except for bulk imports of directories
previously maintained in CVS elsewhere (e.g. libjava).
What is the exact proposal? That is, what goes in what directory, and
does C become a language that should be named in --enable-languages (and
is included in lang_requires for the other language subdirectories?)?
--
Joseph S. Myers
jsm28@cam.ac.uk