importing another file into top-level include directory?

[Zack Weinberg]

DJ Delorie <dj@redhat.com> writes:

>> Ouch.  The master copy of the code is in gcc repo, but the rules explaining
>> that the master copy of the code is in gcc repo are stored in the src repo,
>> under a filename used for different purposes in the gcc repo.
>
> Well, the gcc folks don't need to know those rules - it just works
> right for them ;-)
>
> Basically, anywhere where a set of sources is *not* the master, is
> where you need information stating that.

It has in fact caused me headaches that not all of the files at the
top level are in sync, when setting up combined trees.  The affected
files are:

COPYING
COPYING.LIB
ChangeLog
MAINTAINERS
README
config-ml.in
install-sh
libtool.m4
ltconfig
ltmain.sh

COPYING and COPYING.LIB should probably be overwritten with whatever
the latest official FSF text is (potential concern is that binutils
COPYING.LIB is 2.0 but gcc COPYING.LIB is 2.1; there might be code
under 2.0 and nothing else; I know I was unimpressed with the changes
in 2.1).

There is no good reason for config-ml.in, install-sh, libtool.m4,
ltconfig, ltmain.sh not to be in sync, but there might be a bad
reason, if you see what I mean.

ChangeLog, MAINTAINERS, and README all contain genuinely different
content.  It might be feasible to merge them, but it would require
thought.  Or we could rename them to ChangeLog.gcc/.src etc.

zw