RFC: Moving C to its own directory

[Andreas Jaeger]

Andreas Jaeger <aj@suse.de> writes:

> Neil Booth <neil@daikokuya.co.uk> writes:
>
>> Following a brief discussion with rth at the summit, and just
>> now on IRC, I thought I'd post what the current plan is.
>>
>> 1) Create a directory fe/
>> 2) Create a directory fe/c/
>> 3) Move c-specific and C common files, like c-lex.c, there.
>> 4) Move objc/ to fe/ too.
>>
>> I originally suggested fe/c/c/ fe/c/cp/ and fe/c/objc, but Zack
>> thought that was overkill and made configury harder, though I
>> still like the separation myself.
>>
>> cp/, f/ and java/ and (ugh) ada/ should be moved too, but I'm not
>> volounteering to do those.
>
> Separating the files so that we have for each "module" or logical unit
> a separate directory, sounds fine!
>
> Will this also result in a backend directory?
>
>> If there are no further comments, I will do 1-4) some time in the
>> future.  I'm quite busy at present, so it'll probably be at least
>> 2 months.
>
> The problem that I see is that moving files around, we lose the CVS
> history.  We could still get to the old versions but cannot do a real
> "cvs annotate".  So, I suggest to do the move in the repository and
> copy the complete files around.

Note that this is not a prerequisite - if we cannot do it, bad
luck. ;-)

We should move forward with your plan in any way since I think it's a
good idea - but if we're able to keep the history that would be even
better.

Andreas
-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj