Moving C to its own directory (was Re: ObjC tree inlining)

[David O'Brien]

On Tue, Nov 20, 2001 at 08:56:31AM +0000, Joseph S. Myers wrote:
> On 20 Nov 2001, Alexandre Oliva wrote:
> > It would be extremely beneficial, I'd strongly suggest us to break
> > this rule in the case of moving the C-specific sources in the GCC
> > repository.  It would be best to copy all C-specific CVS files to the
> > `c' sub-directory, such that you can still do CVS diffs based on
> > dates, but deleting all tags from it, since they were not present in
> > older releases.  Of course, if you check out an old snapshot by date,
> > you'll get additional files in the `c' directory that weren't present
> > back then, but they wouldn't be used at all, because the Makefile
> > fragment for the C language wouldn't be present.
> 
> Doing this thing is a recipe for problems, even if you mark all the old
> revisions "dead" and take care to avoid a file ending up both in and out
> of the Attic.

Specifics of the potenital problems?  FreeBSD has been doing this for
many, many years.

> Some more advanced version control systems might support renaming files in
> a better way, but with CVS we should avoid going behind its back.

Why?
 
-- 
-- David  (obrien@FreeBSD.org)