http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39813
--- Comment #7 from Frédéric Buclin <LpSolit at netscape dot net> 2011-09-29 16:46:08 UTC --- Our code doesn't CC gcc-bugs@gcc.gnu.org by default. This is useless as it already gets bugmails for all bugs in the gcc product thanks to our Bugzilla extension (was so since we upgraded from 2.20 to 3.6.2). If there are some bugs with gcc-bugs@gcc.gnu.org in the CC list, then this comes from old hacks GCC Bugzilla 2.20 had before I did the upgrade. You don't have to worry about this as it has no effect on getting bugmails. Once we upgrade to Bugzilla 4.2 (this won't happen before several months as we didn't release 4.2rc1 yet), powerless users won't be allowed to unCC someone else. We enforced this in 4.2 for the exact same reason as described here, i.e. a user having fun removing another user account from the CC list. If this is critical for overseers, I can backport and apply the patch to GCC Bugzilla.
