This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: auto-sync of top-level 'include' & 'config' directories?
I don't know what list to contact to relaunch the discussion on what
copy of shared file should be the master, feel free to forward
extracts of my patches.
As for the "shared" directories: config from gcc has mt-alphaieee,
config from src has mt-s390pic and mh-s390pic, and include from src has
184 more files than gcc.
If there are no strong feelings, what about gcc being the config
master and src the include master, with a README.COMMON stating:
- patches to include and config must be sent to both xxx-patches
mailing lists
- approval by an authorized person on one of the projects is enough to
commit, if not urgent or new, both approval being better but not
required so patches do not stay stuck forever
- if there's a problem or conflict about a patch, assume that it can
be resolved afterwards by talking
- a bot does the sync every hour or so or automatically at commit
- if there's a lasting conflict, the bot is extended with code to read
gcc/do-not-want-from-src.txt and src/do-not-want-from-gcc.txt and exclude
appropriate files from auto-sync so that both project can endlessly flame
each other
--
Laurent Guerby <guerby@acm.org>