From: Neil Booth <neil@daikokuya.co.uk>
To: Richard.Earnshaw@arm.com
Cc: gcc@gcc.gnu.org
Subject: Re: Bugzilla and gcc-bugs@gcc.gnu.org
Date: Fri, 23 May 2003 20:01:00 -0000 [thread overview]
Message-ID: <20030523200045.GA27341@daikokuya.co.uk> (raw)
In-Reply-To: <200305231026.h4NAQHN06500@pc960.cambridge.arm.com>
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'd like to see bugs that are closed too (in the GNATS sense).
Neil.
prev parent reply other threads:[~2003-05-23 20:00 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
2003-05-23 20:01 ` Neil Booth [this message]
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=20030523200045.GA27341@daikokuya.co.uk \
--to=neil@daikokuya.co.uk \
--cc=Richard.Earnshaw@arm.com \
--cc=gcc@gcc.gnu.org \
/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).