From: Pedro Alves <palves@redhat.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] gdb/testsuite: Add gdb_test_multiple_name variable
Date: Tue, 01 Oct 2019 18:31:00 -0000 [thread overview]
Message-ID: <1d1f200a-00ef-b16b-eb44-a74ada07e70b@redhat.com> (raw)
In-Reply-To: <20191001172850.29867-1-andrew.burgess@embecosm.com>
On 10/1/19 6:28 PM, Andrew Burgess wrote:
> My only regret is that '$gdb_test_multiple_name' is so long, but I
> wanted something that was unlikely to clash with any existing variable
> name, or anything that a user is likely to want to use.
I'd go for "gdb_test_name", without the "multiple". I wouldn't
be surprised if we find other uses for this without calling
gdb_test_multiple directly. I think it's reasonable to claim
that the testsuite itself owns the gdb_ prefix.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2019-10-01 18:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 17:29 Andrew Burgess
2019-10-01 17:41 ` Keith Seitz
2019-10-02 13:03 ` Andrew Burgess
2019-10-02 17:17 ` Keith Seitz
2019-10-03 10:02 ` Andrew Burgess
2019-10-01 18:31 ` Pedro Alves [this message]
2019-10-06 8:24 ` Tom de Vries
2019-10-07 10:28 ` Andrew Burgess
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=1d1f200a-00ef-b16b-eb44-a74ada07e70b@redhat.com \
--to=palves@redhat.com \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
/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