Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Daniel Fellows <daniel.fellows@arm.com>
Cc: <simark@simark.ca>,  <simon.marchi@efficios.com>,
	<gdb-patches@sourceware.org>,  <tom@tromey.com>,  <nd@arm.com>
Subject: Re: [PATCH v2] gdb: use gdb::unordered_{set,map} at a few places
Date: Fri, 21 Aug 2026 09:30:36 -0600	[thread overview]
Message-ID: <87cxvbsd7n.fsf@tromey.com> (raw)
In-Reply-To: <20260814120636.2228546-1-daniel.fellows@arm.com> (Daniel Fellows's message of "Fri, 14 Aug 2026 13:06:36 +0100")

>>>>> "Daniel" == Daniel Fellows <daniel.fellows@arm.com> writes:

Daniel> Having this fix on gdb-17-branch would still help our downstream
Daniel> Arm 16 builds. What would be the best way to get this minimal
Daniel> fix committed to gdb-17-branch?

Send a patch in the usual way and I can approve it; or apply & push it
for you.  A patch just adding an include doesn't need copyright assignment.

thanks,
Tom

      reply	other threads:[~2026-08-21 15:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-13 21:35 [PATCH] " Simon Marchi
2025-11-13 21:43 ` [PATCH v2] " Simon Marchi
2025-11-14 19:49   ` Tom Tromey
2025-11-14 20:00     ` Simon Marchi
2025-11-14 20:05       ` Tom Tromey
2025-11-14 20:32         ` Simon Marchi
2025-11-14 21:10           ` Tom Tromey
2025-11-14 21:15             ` Simon Marchi
2025-11-14 21:43               ` Tom Tromey
2025-11-14 22:20                 ` Simon Marchi
2025-11-17 15:58                   ` Tom Tromey
2025-11-17 16:31                     ` Simon Marchi
2026-07-27 16:21                       ` Daniel Fellows
2026-08-11 15:08                         ` Daniel Fellows
2026-08-13 13:04                         ` Simon Marchi
2026-08-14 12:06                           ` Daniel Fellows
2026-08-21 15:30                             ` Tom Tromey [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=87cxvbsd7n.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=daniel.fellows@arm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nd@arm.com \
    --cc=simark@simark.ca \
    --cc=simon.marchi@efficios.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