From: Andrew Burgess <aburgess@redhat.com>
To: Tom Tromey <tom@tromey.com>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCHv3] gdb: remove attempted type de-duplication when building gdb-index
Date: Tue, 04 Nov 2025 14:23:48 +0000 [thread overview]
Message-ID: <87frat6fm3.fsf@redhat.com> (raw)
In-Reply-To: <87zf9ikg2n.fsf@tromey.com>
Tom Tromey <tom@tromey.com> writes:
> Andrew> I propose to link to the second of these with a 'Bug:' tag in this
> Andrew> commit, but I don't think opening another bug is necessary. Does that
> Andrew> sound OK to you?
>
> Yeah thanks.
Just wanted to leave a status update for this patch. I've not forgotten
to merge this fix, but I rebased ready to merge, and ran
check-all-boards on the new test, which I thought I'd already done, but
I guess not as some additional failures came to light.
These failures are caused by a separate issue for which I've posted a
patch here:
https://inbox.sourceware.org/gdb-patches/c3f68558028752d4405e5ed5a6215c44e81d90b6.1761820190.git.aburgess@redhat.com
Once this is reviewed and merged I'll update this patch and get it
merged.
Thanks,
Andrew
next prev parent reply other threads:[~2025-11-04 14:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 9:36 [PATCH] " Andrew Burgess
2025-10-16 18:11 ` [PATCHv2] " Andrew Burgess
2025-10-21 13:45 ` [PATCHv3] " Andrew Burgess
2025-10-22 15:17 ` Tom Tromey
2025-10-22 15:59 ` Andrew Burgess
2025-10-22 16:13 ` Andrew Burgess
2025-10-22 17:21 ` Tom Tromey
2025-11-04 14:23 ` Andrew Burgess [this message]
2025-10-22 17:21 ` Tom Tromey
2025-11-13 16:32 ` Andrew Burgess
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=87frat6fm3.fsf@redhat.com \
--to=aburgess@redhat.com \
--cc=gdb-patches@sourceware.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