This is the mail archive of the
mailing list for the GCC project.
Re: bugzilla problem
On Wed, 2004-09-29 at 15:35 +0200, Richard Guenther wrote:
> On Wed, 29 Sep 2004 09:25:58 -0400, Daniel Berlin <firstname.lastname@example.org> wrote:
> > On Wed, 2004-09-29 at 09:16 -0400, Andrew Pinski wrote:
> > > On Sep 29, 2004, at 9:08 AM, email@example.com wrote:
> > >
> > > > I created an attachment
> > > > Additional Comment #9 From Michael Cieslinski 2004-09-29 11:11
> > > > to bug report http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16697
> > >
> > > I am going to assume PR 17697.
> > >
> > > > That did not show up in http://gcc.gnu.org/ml/gcc-bugs/ mailing list.
> > > >
> > > > Is that a bug itself? Should I file a bug report for that?
> > >
> > > no this is not a bug, attachments to already confirmed bugs do not
> > > get send to the list.
> > Right.
> > We had a discussion about this some time ago, and the consensus was that
> > people didn't want gcc-bugs to get mail about attachments to already
> > existing bugs.
> It would be nice to have a mail sent in case of a commented new attachment of
> type "patch". Like for PR13770, though manually pinging doesn't seem to trigger
> a semi-automatic apply.
I can do this if we really want it, but it takes it out of the realm of
just setting gcc-bugs email preference checkboxes, and into the realm of
something i've got to special case in the bugmail perl code.
All patches, even those attached to bugzilla, are supposed to be sent to
gcc-patches as well.
So i'm not sure what it buys you to copy a link to them to gcc-bugs as
Giovanni's patch pinger should be able to automatically ping patches
that are on bugzilla and were sent to gcc-patches.
He's been testing it by having it send output to bugzilla-
firstname.lastname@example.org (the bugzilla master mailing list), and it looks
Anyway, if we decide we want to do the above, it'll go onto my bugzilla
The next two things on my bugzilla list are to make patch attachments
auto-add the patch keyword, and to improve x-patch handling for incoming
By that time, 2.18 will probably be out (we are at 2.18rc3), and it'll
be time for another bugzilla merge.