On 2010/11/8 下午 07:01, Andrew Stubbs wrote:
Here's my proposal:
Create a new Launchpad branch for GCC 4.6.
Synchronize this branch with upstream regularly
- once per week, perhaps.
Try to get upstream approval for all new patches in the usual way
- on the understanding that they won't be applied until stage 1
- bug fixes are unaffected and may commit as usual.
Commit all pending patches to our own 4.6 branch
- and backport them to our 4.5, branch, of course.
Usual "no test regressions" policy applies to our own patches
- but beware regressions from merges from upstream.
- we may want to track the clean 4.6 test results for comparison
This is little different to what we do with the 4.5 release branch now.
This looks fine, it actually isn't that much different from what we're doing now, except using another branch to hold our changes.
Still, I would like to see a 'linaro-trunk' branch under svn://gcc.gnu.org/svn/branches. It would actually serve a different purpose than a LP branch; the LP GCC 4.6 would probably eventually turn into Linaro 4.6, while a SVN branch would be a preparation for re-merging into mainline trunk when 4.7-stage1 opens. Also, for the GCC community, a SVN branch would probably be more convenient.
We can have our patches submitted to gcc-patches, and have it reviewed under the usual [patch, <branch>] format, rather than the odd condition where we ask for approval, then accumulate in an outside repository.
Chung-Lin