Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: Re: [ob] Eliminate another gdb_suppress_entire_file
Date: Fri, 23 Jun 2006 04:04:00 -0000	[thread overview]
Message-ID: <20060623040352.GK976@adacore.com> (raw)
In-Reply-To: <20060623033948.GA3253@nevyn.them.org>

> I've been using untested followed by return.  Why wouldn't that be
> ideal?

It's actually pretty good. I think in some cases unsupported might
be a better choice, but I like untested too, because it's always
going to be true...

I see in your patch that you used the name of the .exp file as
the argument of untested. Should we do that, or should we try
to preserve the string we previously used with gdb_suppress_entire_file?

-- 
Joel


  reply	other threads:[~2006-06-23  4:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-22 19:58 Daniel Jacobowitz
2006-06-23  3:11 ` Joel Brobecker
2006-06-23  3:22   ` Daniel Jacobowitz
2006-06-23  3:35     ` Joel Brobecker
2006-06-23  3:40       ` Daniel Jacobowitz
2006-06-23  4:04         ` Joel Brobecker [this message]
2006-06-23 12:34           ` Daniel Jacobowitz

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=20060623040352.GK976@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.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