auto-sync of top-level 'include' & 'config' directories?

[guerby@acm.org]

> Include is not a problem.  I've said that MANY times and it hasn't
> sunk in yet.  The libiberty and include directories are already as
> in-sync as they're going to get, and an auto-sync cron job keeps them
> that way.

Okay sorry for my ignorance, I'm pretty new to all those projects and
their common and not-common aspects. To help people that will follow
the same path as me, could you put a README.GCC in include and/or
libiberty (or wherever is best) documenting the how and why of the
current situation?  

That should take care of the "sunk in yet" for the people that haven't
followed in detail a dozen of GNU mailing lists for the past decade,
but that do bother reading documentation when it exists and not hidden
in a too remote directory :).

> > - a bot does the sync every hour or so or automatically at commit
> 
> No.  I review every patch before merging, because it's not safe to
> truly auto-merge changes that way.

Okay so you're the bot :). What about the diff to non doc files I saw?
Should I submit a cleaned up patch, if so from what source to what
target and to what mailing lists? Or will you take care of that?

Thank you for your time,

-- 
Laurent Guerby <guerby@acm.org>