http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55376
--- Comment #5 from Konstantin Serebryany <konstantin.s.serebryany at gmail dot com> 2012-11-20 05:40:34 UTC --- Merging in both directions is possible, but painful, so I'd prefer to limit it. How about this phrasing? === All changes in this directory should be pre-approved by one of the maintainers. Trivial and urgent fixes (portability, build fixes, etc) may go directly to the gcc tree. All non-trivial changes, functionality improvements, etc should go through the upstream tree first and then be merged back to the gcc tree. === I also want to have a semi-automated way to pull the updates from upstream. What is the preferred scripting language? Is bash (python, perl) ok? When pulling a new update, what text do we expect in the ChangeLog? Is the upstream SVN revision enough, or we want to copy all commit messages?
