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?
> 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?
The current merges are all in the gcc->src direction, and it's
documented on the src side.
> Okay so you're the bot :)
Well, I have cron jobs, but I push the "go" button when they tell me
something is pending.
> 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?
It's a bit harder than that. First, you have to choose the files to
merge and which to not merge. You can't merge MAINTAINERS, for
example. Merging Makefile/configure/configure.in would be useful.
Then, you have to read the ChangeLogs to see which changes came from
which sides, so you don't accidentally revert someone else's change.
Then, submit a patch for each side to add the relevent patches to the
other side, which brings them in sync by making sure they both have
all the patches.
Once a given file *is* in sync, let me know and I'll take it from
there.