From: Andrew Cagney <ac131313@redhat.com>
To: gdb@sources.redhat.com
Subject: Re: GDB `cannotfix' pr state, require PR with xfail `moving forward'.
Date: Fri, 17 Jan 2003 19:26:00 -0000 [thread overview]
Message-ID: <3E2858DC.4030405@redhat.com> (raw)
In-Reply-To: <3E270973.9020702@redhat.com>
With revisions:
> There is currently a long thread (Remove all setup_xfail...)'s on gdb-patches@. Several proposals, I think, can already be identified at this point in the discussion.
>
> - yank the existing xfail PR markings (but not the actual xfails) (they apply to old internal Red Hat and HP bug databases and hence are meaningless).
Still stands.
> - `moving forward' all new xfails, and all modifications to existing xfail's should include a bug report (this way, new analyzed vs old unanalized xfail's can easily be differentiated).
Still stands.
> - GDB have a new closed state `cannotfix'; or a new class `xfail' or `notabug' or ...; or even reuse the class `mistaken' that can be used to categorize xfail bug reports (not sure which is better here).
GDB has a new category `external'. External bugs can either be
`suspended' (I guess that implies that the bug is waiting on the
external code to be fixed), or `closed' the external problem has been fixed.
Andrew
next prev parent reply other threads:[~2003-01-17 19:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-16 19:35 Andrew Cagney
2003-01-17 19:26 ` Andrew Cagney [this message]
2003-01-17 19:29 ` Daniel Jacobowitz
2003-01-17 19:47 ` Andrew Cagney
2003-01-17 19:40 ` David Carlton
2003-01-17 19:56 ` Andrew Cagney
2003-01-17 19:45 Michael Elizabeth Chastain
2003-01-17 19:46 ` Daniel Jacobowitz
2003-01-17 20:12 ` Andrew Cagney
2003-01-17 20:18 ` Daniel Jacobowitz
2003-01-17 20:53 ` Andrew Cagney
2003-01-17 22:06 ` Daniel Jacobowitz
2003-01-17 23:28 ` Andrew Cagney
2003-01-18 3:40 ` Daniel Jacobowitz
2003-01-17 20:16 ` Andrew Cagney
2003-01-17 19:57 Michael Elizabeth Chastain
2003-01-17 20:03 Michael Elizabeth Chastain
2003-01-17 20:28 Michael Elizabeth Chastain
2003-01-18 11:33 ` Eli Zaretskii
2003-01-17 20:52 Michael Elizabeth Chastain
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=3E2858DC.4030405@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb@sources.redhat.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