public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Daniel Berlin <dberlin@dberlin.org>
To: Volker Reichelt <reichelt@igpm.rwth-aachen.de>
Cc: giovannibajo@libero.it, bangerth@ices.utexas.edu,
	gcc@gcc.gnu.org, gdr@integrable-solutions.net,
	ehrhardt@mathematik.uni-ulm.de
Subject: Re: Suggestion for new keywords in bugzilla
Date: Thu, 22 May 2003 16:21:00 -0000	[thread overview]
Message-ID: <863FF44C-8C6F-11D7-85C9-000A95A34564@dberlin.org> (raw)
In-Reply-To: <200305221535.h4MFZINZ008968@relay.rwth-aachen.de>

>
>> I'm not sure what it's best option. Of course, everything is better 
>> than the
>> [diagnosis] stamp in the summary.
>
>>> * error-recovery (we get an ICE/bailing-out-message after a sensible
>>>   error message). This should be specified in addition to
>>>   ice-on-invalid-code.
>>
>> Yes, agreed. Is it possible to have some dropbox with keywords 
>> instead of
>> being forced to type them in manually?
This is being worked on by someone else (If you look at 
bugzilla.mozilla.org's bugzilla bugs, you'll see one for this 
enhancement).
When they get it done, i'll add it to our bugzilla.

  reply	other threads:[~2003-05-22 16:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-22 16:07 Volker Reichelt
2003-05-22 16:21 ` Daniel Berlin [this message]
  -- 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 17:24 Nathanael Nerode
2003-05-22 18:19 ` Michael S. Zick
2003-05-22 18:21 ` Joseph S. Myers
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=863FF44C-8C6F-11D7-85C9-000A95A34564@dberlin.org \
    --to=dberlin@dberlin.org \
    --cc=bangerth@ices.utexas.edu \
    --cc=ehrhardt@mathematik.uni-ulm.de \
    --cc=gcc@gcc.gnu.org \
    --cc=gdr@integrable-solutions.net \
    --cc=giovannibajo@libero.it \
    --cc=reichelt@igpm.rwth-aachen.de \
    /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).