From: Yao Qi <yao@codesourcery.com>
To: Pedro Alves <palves@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: tstatus.exp: use UNSUPPORTED for optional features that are not supported
Date: Wed, 06 Mar 2013 01:14:00 -0000 [thread overview]
Message-ID: <5136982D.9040108@codesourcery.com> (raw)
In-Reply-To: <51364143.30302@redhat.com>
Pedro,
The patch looks pretty good to me.
On 03/06/2013 03:02 AM, Pedro Alves wrote:
> + set test "tstatus reports trace note"
> gdb_test_multiple "tstatus" "check on trace status" {
^^^^^^^^^^^^^^^^^^^^^^ use $test here.
--
Yao (é½å°§)
next prev parent reply other threads:[~2013-03-06 1:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 15:37 [PATCH] Fix a bug in tstatus.exp matching tstatus output Yao Qi
2013-03-04 16:23 ` Joel Brobecker
2013-03-04 17:35 ` Tom Tromey
2013-03-05 2:24 ` Yao Qi
2013-03-05 19:09 ` Pedro Alves
2013-03-04 16:32 ` Pedro Alves
2013-03-05 2:39 ` Yao Qi
2013-03-05 19:02 ` tstatus.exp: use UNSUPPORTED for optional features that are not supported (was: Re: [PATCH] Fix a bug in tstatus.exp matching tstatus output) Pedro Alves
2013-03-06 1:14 ` Yao Qi [this message]
2013-03-06 12:19 ` tstatus.exp: use UNSUPPORTED for optional features that are not supported Pedro Alves
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=5136982D.9040108@codesourcery.com \
--to=yao@codesourcery.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