Re: GCC review process: how to handle external submissions

[Daniel Berlin <dberlin at dberlin dot org>]

On Tuesday, March 11, 2003, at 06:52  PM, Craig Rodrigues wrote:

> On Tue, Mar 11, 2003 at 06:29:02PM -0500, Daniel Berlin wrote:
> > I'm a little unclear on what exactly you guys want (IE by "Bugzilla
> > address" do you mean seperate addresses for each bug or what) , but if
> > you hash it out and let me know, i should be able to make it happen.
>
> If I subscribe to gcc-bugs at gcc dot gnu dot org, I should see messages generated
> by Bugzilla with the following headers:
>
>  Return-Path: <gcc-bugzilla at gcc dot gnu dot org>
>  From: gcc-bugzilla at gcc dot gnu dot org
>  To: user1 at someplace, user2 at someplace
>  Date: some date
>  Subject: [Bug 4835] bug subject line
>  Message-Id: <some message ID>
>
>
> If I reply this message, the following should happen:
>    -> the database entry for bug 4835 will get updated with my reply
This will happen

>    -> all e-mail addresses which are registered in the Bugzilla 
> database
>       for bug 4835 will get copies of this reply.  These e-mail 
> addresses
>       ( user1 at someplace, user2 at someplace) will appear in the To: field
This will happen because the comments will have changed, and it will 
send bug changed mail.

>    -> Bugzilla will magically send a copy of this message
>       to gcc-bugs at gcc dot gnu dot org, but gcc-bugs at gcc dot gnu dot org will not appear
>       anywhere in the e-mail header.  That way, if I reply to this 
> message,
>       it will go to gcc-bugzilla.
I'll make it bcc bug changes to gcc-bugs.

> Does this make sense?
Yup.

> Thanks.
> --
> Craig Rodrigues
> http://home.attbi.com/~rodrigc
> rodrigc at attbi dot com