From: Nathanael Nerode <neroden@twcny.rr.com>
To: gcc@gcc.gnu.org
Subject: Re: Suggestion for new keywords in bugzilla
Date: Thu, 22 May 2003 17:24:00 -0000 [thread overview]
Message-ID: <20030522171302.GA548@doctormoo> (raw)
On 22 May, Giovanni Bajo wrote:
> Volker Reichelt <reichelt@igpm.rwth-aachen.de> wrote:
<snip>
>> * diagnostic (for error messages/warnings that are misleading or
broken
>> and superfluous/missing warnings)
I actually thought that there should be two keywords for this:
missing-diagnostic (There should be a warning, but there isn't.)
misleading-diagnostic (There's a warning which shouldn't be there, or
should be replaced by a different warning.)
Better names are solicited.
--Nathanael
next reply other threads:[~2003-05-22 17:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-22 17:24 Nathanael Nerode [this message]
2003-05-22 18:19 ` Michael S. Zick
2003-05-22 18:21 ` Joseph S. Myers
-- strict thread matches above, loose matches on Subject: below --
2003-05-23 10:36 Volker Reichelt
2003-05-23 15:34 ` Nathanael Nerode
2003-05-23 10:26 Giovanni Bajo
2003-05-23 15:45 ` Nathanael Nerode
2003-05-27 14:03 ` Giovanni Bajo
2003-05-22 17:56 Nathanael Nerode
2003-05-22 16:07 Volker Reichelt
2003-05-22 16:21 ` Daniel Berlin
2003-05-22 12:56 Volker Reichelt
2003-05-22 15:13 ` Giovanni Bajo
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=20030522171302.GA548@doctormoo \
--to=neroden@twcny.rr.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).