From: Tom Tromey <tom@tromey.com>
To: "Willgerodt, Felix" <felix.willgerodt@intel.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
"tom@tromey.com" <tom@tromey.com>,
"keiths@redhat.com" <keiths@redhat.com>
Subject: Re: [PATCH v2 1/1] gdb: Fix segfault with a big .dynamic section size
Date: Mon, 20 Nov 2023 09:21:39 -0700 [thread overview]
Message-ID: <87h6lgz97w.fsf@tromey.com> (raw)
In-Reply-To: <MN2PR11MB4566A57A89F289ED06E6A8098EB4A@MN2PR11MB4566.namprd11.prod.outlook.com> (Felix Willgerodt's message of "Mon, 20 Nov 2023 15:21:32 +0000")
>>>>> Willgerodt, Felix <felix.willgerodt@intel.com> writes:
> Sorry to ping so early again, but I see that you approved v1 here:
> https://sourceware.org/pipermail/gdb-patches/2023-November/204074.html
> Since I didn't change much from v1 (commit msg and the variable type),
> can I just merge this v2?
Yes, sorry about any confusion.
Tom
next prev parent reply other threads:[~2023-11-20 16:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 15:42 Felix Willgerodt
2023-11-20 15:21 ` Willgerodt, Felix
2023-11-20 16:21 ` Tom Tromey [this message]
2023-11-21 8:08 ` Willgerodt, Felix
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=87h6lgz97w.fsf@tromey.com \
--to=tom@tromey.com \
--cc=felix.willgerodt@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).