From: Michael Elizabeth Chastain <mec@shout.net>
To: carlton@math.stanford.edu, drow@mvista.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch] KFAIL gdb/1025
Date: Tue, 04 Feb 2003 15:32:00 -0000 [thread overview]
Message-ID: <200302041511.h14FBYB15327@duracef.shout.net> (raw)
drow> I'm really not comfortable with this use of KFAIL. My hope was that we
drow> would analyze particular failures before KFAILing them off to oblivion.
drow> I spent time fixing these exact six failures a bit under a month ago;
drow> if it isn't working for your setup I want more information.
Well, there's a tension between 'getting work done' and 'checking
with other people'. In this particular case, waiting a few hours
would have drawn some info from me and Daniel J. We can't win them
all.
I'm more concerned about the 'KFAILing them off to oblivion'.
I foresee that we are going to have a culture clash over KFAIL.
To me, KFAIL means that the bug is known; but to everybody else,
it's going to take on the meaning that the bug is low-priority.
These properties are orthogonal but I can see KFAIL taking on that
twisted connotation.
Michael C
next reply other threads:[~2003-02-04 15:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-04 15:32 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-07 17:40 Michael Elizabeth Chastain
2003-02-07 17:46 ` David Carlton
2003-02-07 17:08 Michael Elizabeth Chastain
2003-02-07 17:13 ` David Carlton
2003-02-07 16:16 Michael Elizabeth Chastain
2003-02-07 17:04 ` David Carlton
2003-02-05 6:04 Michael Elizabeth Chastain
2003-02-04 20:07 Michael Elizabeth Chastain
2003-02-04 18:33 Michael Elizabeth Chastain
2003-02-04 1:18 David Carlton
2003-02-04 14:44 ` Daniel Jacobowitz
2003-02-04 17:17 ` David Carlton
2003-02-04 17:22 ` Daniel Jacobowitz
2003-02-04 22:28 ` David Carlton
2003-02-06 20:59 ` David Carlton
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=200302041511.h14FBYB15327@duracef.shout.net \
--to=mec@shout.net \
--cc=carlton@math.stanford.edu \
--cc=drow@mvista.com \
--cc=gdb-patches@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