From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Subject: Re: GDB `cannotfix' pr state, require PR with xfail `moving forward'.
Date: Fri, 17 Jan 2003 20:18:00 -0000 [thread overview]
Message-ID: <20030117201841.GA14124@nevyn.them.org> (raw)
In-Reply-To: <3E2863B3.6010207@redhat.com>
On Fri, Jan 17, 2003 at 03:12:35PM -0500, Andrew Cagney wrote:
>
> >In that case I'd want "broken in all GCC's" to be open rather than
> >suspended. Does this bother anyone?
>
> Yes, that bothers me, it would be wrong. The only time a PR is in the
> open state is when no one has looked at it. As soon as someone looks at
> the PR, it should be changed from open to some other state - analized,
> suspended, closed, ...
Substitute "a state other than suspended or closed". Better? Probably
"analyzed".
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-01-17 20:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2003-01-17 20:52 Michael Elizabeth Chastain
2003-01-17 20:28 Michael Elizabeth Chastain
2003-01-18 11:33 ` Eli Zaretskii
2003-01-17 20:03 Michael Elizabeth Chastain
2003-01-17 19:57 Michael Elizabeth Chastain
2003-01-16 19:35 Andrew Cagney
2003-01-17 19:26 ` Andrew Cagney
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
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=20030117201841.GA14124@nevyn.them.org \
--to=drow@mvista.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