From: "Christoph Müllner" <christoph.muellner@vrull.eu>
To: mailing-list@organisation.org, gdb-patches@sourceware.org,
Chris Packham <judge.packham@gmail.com>,
Tom Tromey <tom@tromey.com>
Cc: "Christoph Müllner" <christoph.muellner@vrull.eu>
Subject: Re: [PATCH] readline/tcap.h: Update definitions for C23
Date: Mon, 9 Jun 2025 19:17:59 +0200 [thread overview]
Message-ID: <20250609171759.3658611-1-christoph.muellner@vrull.eu> (raw)
In-Reply-To: <20250430044944.1146925-1-judge.packham@gmail.com>
This patch from Apr 30, 2025 landed as 5c87b330e91 on master.
Would it be possible to apply it to gdb-16-branch as well?
The patch applies cleanly.
Thanks,
Christoph
next prev parent reply other threads:[~2025-06-09 17:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 4:49 Chris Packham
2025-04-30 19:30 ` Tom Tromey
2025-04-30 20:44 ` Chris Packham
2025-05-02 18:03 ` Tom Tromey
2025-06-09 17:17 ` Christoph Müllner [this message]
2025-06-09 19:46 ` Simon Marchi
2025-06-09 21:43 ` Christoph Müllner
2025-06-10 13:04 ` Tom Tromey
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=20250609171759.3658611-1-christoph.muellner@vrull.eu \
--to=christoph.muellner@vrull.eu \
--cc=gdb-patches@sourceware.org \
--cc=judge.packham@gmail.com \
--cc=mailing-list@organisation.org \
--cc=tom@tromey.com \
/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