Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: ac131313@cygnus.com, drow@mvista.com,
	gdb-patches@sources.redhat.com, rob@welcomehome.org
Subject: Re: RFC: KFAILs [Was: [RFA/mi-testsuite] XFAIL mi*-console.exp]
Date: Fri, 05 Apr 2002 12:07:00 -0000	[thread overview]
Message-ID: <3CAE027E.8540D04B@redhat.com> (raw)
In-Reply-To: <200204051909.g35J99P32716@duracef.shout.net>

Michael Elizabeth Chastain wrote:
> 
> Actually I prefer the pair "kpass/kfail" to "xpass/kfail" and "xpass/xfail"!
> "xpass/kfail" looks weird and lets in some ambiguity.  Can you implement it
> as "kpass/kfail"?
> 
> fna> I can change things to accept the second form like setup_xfail does
> fna> and just make sure that one with no '-' in it was found (the bug id)
> fna> and error out if none was found.  Just let me know if you prefer
> fna> this instead of the positional first argument (I am now having
> fna> second thoughts about that).
> 
> I don't have a strong preference.  (It sounds like you don't either).
> 

Yes, I don't mind one way or another.  But I am more inclined to keep
things as similar as the ones that exist for xfail to avoid confusion.
So, I will only make the bug identification mandatory and keep the
rest the same as for setup_xfail (unless someone has a good argument 
for us to do differently -- I could not think of a good one).

-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9


  reply	other threads:[~2002-04-05 20:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-05 11:09 Michael Elizabeth Chastain
2002-04-05 12:07 ` Fernando Nasser [this message]
2002-04-07 16:30 ` Rob Savoye
2002-04-08  8:41   ` Fernando Nasser
  -- strict thread matches above, loose matches on Subject: below --
2002-04-08  8:59 Michael Elizabeth Chastain
2002-04-08  9:06 ` Fernando Nasser
2002-04-07 17:31 Michael Elizabeth Chastain
2002-04-07 17:38 ` Rob Savoye
2002-04-07 16:53 Michael Elizabeth Chastain
2002-04-07 17:02 ` Rob Savoye
2002-04-05 11:14 Michael Elizabeth Chastain
2002-04-07 16:35 ` Rob Savoye
2002-04-05  9:53 Michael Elizabeth Chastain
2002-04-05 10:22 ` Daniel Jacobowitz
2002-04-05 13:45   ` Andrew Cagney
2002-04-05 13:51     ` Daniel Jacobowitz
2002-04-05 10:23 ` Fernando Nasser
2002-04-05  7:23 [RFA/mi-testsuite] XFAIL mi*-console.exp Michael Elizabeth Chastain
2002-04-05  7:58 ` RFC: KFAILs [Was: [RFA/mi-testsuite] XFAIL mi*-console.exp] Fernando Nasser

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=3CAE027E.8540D04B@redhat.com \
    --to=fnasser@redhat.com \
    --cc=ac131313@cygnus.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec@shout.net \
    --cc=rob@welcomehome.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