------- Comment #27 from LpSolit at netscape dot net 2010-07-15 23:04 ------- For those who are interested, I'm on vacation till mid-August, meaning that I have some free time to help upgrading GCC Bugzilla to 3.6.1.
As it's not acceptable to play with a production installation, we would need a test installation on which we can apply patches and test them (we could file bugs and attach patches to the test installation directly, so that we can test the installation for real). Once everybody is happy with how things work, and thinks everything which is needed has been ported to the new installation, we can make a monolithic patch with all changes in it, and attach it to this bug for the record (as the test installation will probably go away once the upgrade process is complete). The only efficient way I know to customize a Bugzilla installation is to use e.g. CVS or bzr to apply patches, and let the test installation be upgraded from there, so that we can easily generate patches and back them out. Else it's going to be a mess pretty quickly. Is this doable by the GCC team? Else I would have to do it locally, and apply patches manually to the test installation, meaning that I would be the only one able to generate patches on top of other patches. What do you think? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011
