From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: "Ulrich Weigand" <uweigand@de.ibm.com>
Subject: Re: siginfo patches cause testsuite failure?
Date: Fri, 03 Apr 2009 17:21:00 -0000 [thread overview]
Message-ID: <200904031821.49968.pedro@codesourcery.com> (raw)
In-Reply-To: <200904031634.n33GYNYG013021@d12av02.megacenter.de.ibm.com>
On Friday 03 April 2009 17:34:23, Ulrich Weigand wrote:
> I guess in a way that is to be expected, as we now *have* this
> convenience variable always defined ... Should the test case
> be updated?
This has been on my TODO for a while, but haven't gotten to
it yet... I wanted to see if we can delay creating the
variable a bit, but it may be more trouble that it is
worth.
I think we should just update the test.
--
Pedro Alves
prev parent reply other threads:[~2009-04-03 17:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 16:35 Ulrich Weigand
2009-04-03 17:21 ` Pedro Alves [this message]
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=200904031821.49968.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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