From: Andrew Pinski <pinskia@physics.uc.edu>
To: Jason Thorpe <thorpej@wasabisystems.com>
Cc: Andrew Pinski <pinskia@physics.uc.edu>,
Richard.Earnshaw@arm.com, gcc@gcc.gnu.org
Subject: Re: Bugzilla and gcc-bugs@gcc.gnu.org
Date: Fri, 23 May 2003 14:59:00 -0000 [thread overview]
Message-ID: <167DF63A-8D2F-11D7-BA60-000393A6D2F2@physics.uc.edu> (raw)
In-Reply-To: <C65ABB48-8D26-11D7-82D7-000A957650EC@wasabisystems.com>
Think it should be the opposite as it was under GNAT.
Thanks,
Andrew Pinski
On Friday, May 23, 2003, at 09:59 US/Eastern, Jason Thorpe wrote:
>
> On Friday, May 23, 2003, at 03:26 AM, Richard Earnshaw wrote:
>
>> I'd like to suggest that gcc-bugs be used only for NEW reports being
>> entered into bugzilla, and that some other list (maybe the currently
>> defunct gcc-prs) be used for all audit-trail mailings and follow-ups.
>
> I think this is a great idea. It would certainly help me keep up with
> it.
>
> -- Jason R. Thorpe <thorpej@wasabisystems.com>
>
>
>
next prev parent reply other threads:[~2003-05-23 14:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-23 10:32 Richard Earnshaw
2003-05-23 14:15 ` Jason Thorpe
2003-05-23 14:59 ` Andrew Pinski [this message]
2003-05-23 20:01 ` Neil Booth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=167DF63A-8D2F-11D7-BA60-000393A6D2F2@physics.uc.edu \
--to=pinskia@physics.uc.edu \
--cc=Richard.Earnshaw@arm.com \
--cc=gcc@gcc.gnu.org \
--cc=thorpej@wasabisystems.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).