From: Pedro Alves <palves@redhat.com>
To: Markus Metzger <markus.t.metzger@intel.com>
Cc: jan.kratochvil@redhat.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] test, btrace: update expected text
Date: Thu, 16 Jan 2014 09:23:00 -0000 [thread overview]
Message-ID: <52D7A4F0.90702@redhat.com> (raw)
In-Reply-To: <1389862708-17590-1-git-send-email-markus.t.metzger@intel.com>
On 01/16/2014 08:58 AM, Markus Metzger wrote:
> The error message for starting recording twice changed.
> Update the expected text to fix resulting regressions.
>
> 2014-01-16 Markus Metzger <markus.t.metzger@intel.com>
>
> * gdb.btrace/enable.exp: Update expected text.
OK, thanks.
Sorry I missed this, the btrace tests are skipped on my
box (because it doesn't support btrace)...
--
Pedro Alves
prev parent reply other threads:[~2014-01-16 9:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 8:58 Markus Metzger
2014-01-16 9:23 ` 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=52D7A4F0.90702@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=markus.t.metzger@intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).