From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: Neil Booth <neil@daikokuya.co.uk>
Cc: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>, <gcc@gcc.gnu.org>
Subject: Re: New GNATS category request
Date: Tue, 10 Dec 2002 14:44:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0212102232140.23616-100000@kern.srcf.societies.cam.ac.uk> (raw)
In-Reply-To: <20021210220808.GB24163@daikokuya.co.uk>
On Tue, 10 Dec 2002, Neil Booth wrote:
> "driver", pretty please. Many bugs in the driver get stuffed anywhere from
> "c", to "other" and "preprocessor".
If we're adding new categories now (not waiting for Bugzilla), "target" is
long overdue to have separate categories for the main CPU and OS targets
split off (target-i386, target-sparc, target-linux-gnu, ...).
(Previously requested.) That way target maintainers can more easily
select the bugs actually relevant to them.
Note new categories need documenting in gnats.html and gccbug.in, as noted
in the internals manual for adding new front ends (Anatomy of a Language
Front End). If categories for separate targets are added there should be
a similar entry in "Anatomy of a Target Back End", although not all
targets necessarily need their own categories, only reasonably popular
ones (inflation of the number of categories too much might confuse
submitters).
--
Joseph S. Myers
jsm28@cam.ac.uk
next prev parent reply other threads:[~2002-12-10 22:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 14:11 Neil Booth
2002-12-10 14:44 ` Joseph S. Myers [this message]
2002-12-27 10:27 ` Gerald Pfeifer
2003-01-01 22:54 ` Neil Booth
2003-01-02 0:09 ` Gerald Pfeifer
2003-01-02 5:24 ` Neil Booth
2003-01-02 5:27 ` Neil Booth
2003-01-02 8:45 ` Gerald Pfeifer
2002-12-10 16:19 Wolfgang Bangerth
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=Pine.LNX.4.33.0212102232140.23616-100000@kern.srcf.societies.cam.ac.uk \
--to=jsm28@cam.ac.uk \
--cc=gcc@gcc.gnu.org \
--cc=neil@daikokuya.co.uk \
--cc=pfeifer@dbai.tuwien.ac.at \
/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).