From: Keith Seitz <keiths@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: "gdb-patches@sourceware.org ml" <gdb-patches@sourceware.org>
Subject: Re: [RFA] Suppress stap-trace.exp when compilation fails
Date: Wed, 23 May 2012 18:21:00 -0000 [thread overview]
Message-ID: <4FBD2AAD.9020509@redhat.com> (raw)
In-Reply-To: <4FBD203E.1010004@redhat.com>
On 05/23/2012 10:37 AM, Pedro Alves wrote:
> Sure, thanks. There's a second compilation further below, but I'll assume that if
> the first succeeds, the second should also.
I thought the same thing, too, but perhaps there is no reason /not/ to
protect that, too.
I've committed the patch with that safeguard added. [I'm not reposting
that, since it is trivial.]
Thank you for taking a look.
Keith
prev parent reply other threads:[~2012-05-23 18:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 17:15 Keith Seitz
2012-05-23 17:34 ` Sergio Durigan Junior
2012-05-23 17:37 ` Pedro Alves
2012-05-23 18:21 ` Keith Seitz [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=4FBD2AAD.9020509@redhat.com \
--to=keiths@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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