From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/testsuite] Fix gdb.cp/step-and-next-inline.exp with -fcf-protection
Date: Fri, 30 Dec 2022 14:01:10 +0100 [thread overview]
Message-ID: <c5e33968-8fc3-a0cb-3244-651e3cc6556d@suse.de> (raw)
In-Reply-To: <2feda36aa35dd25ac27cba5b7ae86f2c@suse.de>
On 12/23/22 09:14, tdevries via Gdb-patches wrote:
Pushed.
Thanks,
- Tom
prev parent reply other threads:[~2022-12-30 13:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 8:14 tdevries
2022-12-30 13:01 ` Tom de Vries [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=c5e33968-8fc3-a0cb-3244-651e3cc6556d@suse.de \
--to=tdevries@suse.de \
--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).