This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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
branches.

I don't think we have a choice; we need to "cvs remove; cvs add".

--
Mark Mitchell                   mark@codesourcery.com
CodeSourcery, LLC               http://www.codesourcery.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]