From: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] [gdb/testsuite] Add gdb.dwarf2/debug-names-tu.exp
Date: Tue, 6 Sep 2022 10:17:29 +0200 [thread overview]
Message-ID: <44d5a746-6059-e3cb-bde6-7243fb70e769@suse.de> (raw)
In-Reply-To: <20220808142313.29995-1-tdevries@suse.de>
On 8/8/22 16:23, Tom de Vries via Gdb-patches wrote:
I've pushed this series.
Thanks,
- Tom
prev parent reply other threads:[~2022-09-06 8:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 14:23 Tom de Vries via Gdb-patches
2022-08-08 14:23 ` [PATCH 2/2] [gdb/testsuite] Add gdb.dwarf2/debug-names-bad-cu-index.exp Tom de Vries via Gdb-patches
2022-09-06 8:17 ` Tom de Vries via Gdb-patches [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=44d5a746-6059-e3cb-bde6-7243fb70e769@suse.de \
--to=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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