From: Daniel Fellows <daniel.fellows@arm.com>
To: <ciaranwoodward@xmos.com>
Cc: <gdb-patches@sourceware.org>, <tom@tromey.com>, <nd@arm.com>
Subject: Re: [PATCH 1/1] gdb/tui: Fix build for older ncurses
Date: Tue, 28 Jul 2026 14:38:21 +0100 [thread overview]
Message-ID: <20260728133821.1305171-1-daniel.fellows@arm.com> (raw)
In-Reply-To: <MI3PR09MB8624C424FF3F0BDF7DF0E063B9CB2@MI3PR09MB8624.eurprd09.prod.outlook.com>
Hi Ciaran,
Thanks for getting back to me. Yes, if you could push the backport once
the required approval is confirmed, that would be great.
Hopefully one of the maintainers can confirm the correct backport
process and provide approval.
Cheers,
Daniel
prev parent reply other threads:[~2026-07-28 13:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 18:30 Ciaran Woodward
2025-09-12 15:04 ` Tom Tromey
2025-09-12 17:17 ` Ciaran Woodward
2026-07-27 16:15 ` Daniel Fellows
2026-07-28 13:29 ` Ciaran Woodward
2026-07-28 13:38 ` Daniel Fellows [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=20260728133821.1305171-1-daniel.fellows@arm.com \
--to=daniel.fellows@arm.com \
--cc=ciaranwoodward@xmos.com \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.com \
--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