Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Christoph Müllner" <christoph.muellner@vrull.eu>
To: Simon Marchi <simark@simark.ca>
Cc: mailing-list@organisation.org, gdb-patches@sourceware.org,
	 Chris Packham <judge.packham@gmail.com>,
	Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH] readline/tcap.h: Update definitions for C23
Date: Mon, 9 Jun 2025 23:43:07 +0200	[thread overview]
Message-ID: <CAEg0e7jUenVTEJ7fPGqm=H83OvZ-dWSkAUdBU7MZD7hECdfPug@mail.gmail.com> (raw)
In-Reply-To: <0093279e-2e41-4455-a4bb-c93df062d81f@simark.ca>

On Mon, Jun 9, 2025 at 9:46 PM Simon Marchi <simark@simark.ca> wrote:
>
> On 6/9/25 1:17 PM, Christoph Müllner wrote:
> > 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
>
> There (probably) won't be any more GDB 16 releases, but I think it can
> be useful for some people to backport the patch anyway.  We need to have
> a Bugzilla PR number first (if there isn't one already).

The patch on master does not have a PR, and I could not find anything
related to this issue in Bugzilla. Therefore, I've created a PR for
the backport:
  https://sourceware.org/bugzilla/show_bug.cgi?id=33071

For me, a backport to gdb-16-branch is enough.

Thanks,
Christoph


>
> Simon

  reply	other threads:[~2025-06-09 21:43 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
2025-06-09 19:46   ` Simon Marchi
2025-06-09 21:43     ` Christoph Müllner [this message]
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='CAEg0e7jUenVTEJ7fPGqm=H83OvZ-dWSkAUdBU7MZD7hECdfPug@mail.gmail.com' \
    --to=christoph.muellner@vrull.eu \
    --cc=gdb-patches@sourceware.org \
    --cc=judge.packham@gmail.com \
    --cc=mailing-list@organisation.org \
    --cc=simark@simark.ca \
    --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