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: Mark Mitchell <mark at codesourcery dot com>
- To: Phil Edwards <pedwards at disaster dot jaj dot com>, "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- Cc: Alexandre Oliva <aoliva at redhat dot com>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Wed, 21 Nov 2001 09:13:10 -0800
- Subject: Re: Moving C to its own directory (was Re: ObjC tree inlining)
> If it's a documented procedure in the CVS manual, you can hardly call it
> "going behind its back." Yes, I realize that it's a repository-affecting
> action that doesn't get logged in CVSROOT/history, but I think it would
> be better to preserve individual file history by moving the ,v directly.
> The add&remove method is semantically cleaner, but every C front end file
> would then be at revision 1.
If we just "mv" the files, we will never be able to check out old
I don't think we have a choice; we need to "cvs remove; cvs add".
Mark Mitchell firstname.lastname@example.org
CodeSourcery, LLC http://www.codesourcery.com