From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@polymtl.ca>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Make gdb.mi/user-selected-context-sync.exp use proc_with_prefix
Date: Wed, 09 Nov 2016 15:15:00 -0000 [thread overview]
Message-ID: <79d9a31d-e7dc-0525-0c62-2fa6f87c2613@redhat.com> (raw)
In-Reply-To: <20161109031043.7132-1-simon.marchi@polymtl.ca>
On 11/09/2016 03:10 AM, Simon Marchi wrote:
> Pedro's patch provides a cleaner way to prefix tests with the proc name,
(I've pushed in my patch.)
> so let's use that.
>
> (test_setup); Define with proc_with_prefix.
^
|
+ ':'
:-)
LGTM.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-11-09 15:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 0:19 [PATCH v2 0/5] Support an "unlimited" number of user-defined arguments Pedro Alves
2016-11-09 0:19 ` [PATCH v2 1/5] gdb/testsuite: Introduce "proc_with_prefix" Pedro Alves
2016-11-09 1:56 ` Simon Marchi
2016-11-09 3:10 ` [PATCH] Make gdb.mi/user-selected-context-sync.exp use proc_with_prefix Simon Marchi
2016-11-09 15:15 ` Pedro Alves [this message]
2016-11-09 15:57 ` Simon Marchi
2016-11-09 11:50 ` [PATCH v2 1/5] gdb/testsuite: Introduce "proc_with_prefix" Yao Qi
2016-11-09 0:19 ` [PATCH v2 2/5] Further cleanup/modernization of gdb.base/commands.exp Pedro Alves
2016-11-09 3:02 ` Simon Marchi
2016-11-09 15:56 ` Pedro Alves
2016-11-09 15:59 ` Pedro Alves
2016-11-09 16:09 ` Simon Marchi
2016-11-09 16:16 ` Pedro Alves
2016-11-09 16:25 ` Simon Marchi
2016-11-09 18:51 ` Pedro Alves
2016-11-09 16:22 ` Pedro Alves
2016-11-09 16:37 ` Pedro Alves
2016-11-09 16:41 ` Pedro Alves
2016-11-09 0:19 ` [PATCH v2 3/5] Fix PR 20559 - "eval" command and $arg0...$arg9/$argc substitution Pedro Alves
2016-11-09 0:25 ` [PATCH v2 5/5] Support an "unlimited" number of user-defined arguments Pedro Alves
2016-11-09 0:26 ` [PATCH v2 4/5] Test user-defined gdb commands and arguments stack 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=79d9a31d-e7dc-0525-0c62-2fa6f87c2613@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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