From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/2] Cleanup the gdb.cp/cpcompletion.exp test
Date: Wed, 25 Jan 2023 10:13:52 +0000 [thread overview]
Message-ID: <87sffyx6ov.fsf@redhat.com> (raw)
In-Reply-To: <cover.1673550414.git.aburgess@redhat.com>
Andrew Burgess <aburgess@redhat.com> writes:
> Some minor cleanups / improvements for the gdb.cp/cpcompletion.exp
> test script.
I went ahead and pushed these changes.
Thanks,
Andrew
prev parent reply other threads:[~2023-01-25 10:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 19:08 Andrew Burgess
2023-01-12 19:08 ` [PATCH 1/2] gdb/testsuite: use test_gdb_complete_unique more in C++ tests Andrew Burgess
2023-01-12 19:08 ` [PATCH 2/2] gdb/testsuite: rename test source file to match test script Andrew Burgess
2023-01-25 10:13 ` 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=87sffyx6ov.fsf@redhat.com \
--to=aburgess@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).