From: Andrew Burgess <andrew.burgess@embecosm.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/5] Remove duplicate test names from gdb.cp/*.exp
Date: Fri, 26 Mar 2021 15:03:51 +0000 [thread overview]
Message-ID: <20210326150351.GS5520@embecosm.com> (raw)
In-Reply-To: <cover.1615980148.git.andrew.burgess@embecosm.com>
* Andrew Burgess <andrew.burgess@embecosm.com> [2021-03-17 11:23:56 +0000]:
> Duplicate test name removal in gdb.cp/*.exp. The first 4 patches are
> more significant test changes. The final patch picks up all the
> trivial changes to squash the remaining duplicates.
>
> ---
>
> Andrew Burgess (5):
> gdb/testsuite: remove duplicate test names for gdb.cp/nsusing.exp
> gdb/testsuite: remove duplicate test names from gdb.cp/gdb2384.exp
> gdb/testsuite: remove duplicate test from gdb.cp/maint.exp
> gdb/testsuite: resolve duplicate test name in gdb.cp/cplusfuncs.exp
> gdb/testsuite: resolve remaining duplicate test names in gdb.cp/*.exp
I've now pushed this series.
Thanks,
Andrew
prev parent reply other threads:[~2021-03-26 15:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 11:23 Andrew Burgess
2021-03-17 11:23 ` [PATCH 1/5] gdb/testsuite: remove duplicate test names for gdb.cp/nsusing.exp Andrew Burgess
2021-03-17 11:23 ` [PATCH 2/5] gdb/testsuite: remove duplicate test names from gdb.cp/gdb2384.exp Andrew Burgess
2021-03-17 11:23 ` [PATCH 3/5] gdb/testsuite: remove duplicate test from gdb.cp/maint.exp Andrew Burgess
2021-03-17 11:24 ` [PATCH 4/5] gdb/testsuite: resolve duplicate test name in gdb.cp/cplusfuncs.exp Andrew Burgess
2021-03-17 11:24 ` [PATCH 5/5] gdb/testsuite: resolve remaining duplicate test names in gdb.cp/*.exp Andrew Burgess
2021-03-26 15:03 ` Andrew Burgess [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=20210326150351.GS5520@embecosm.com \
--to=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