From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tromey@adacore.com>
Cc: Simon Marchi <simark@simark.ca>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix two bugs in gdbserver thread name handling
Date: Tue, 09 Jan 2024 07:14:05 -0700 [thread overview]
Message-ID: <87il42wq4y.fsf@tromey.com> (raw)
In-Reply-To: <87sf4377to.fsf@tromey.com> (Tom Tromey's message of "Fri, 15 Dec 2023 09:24:03 -0700")
>>>>> "Tom" == Tom Tromey <tromey@adacore.com> writes:
Simon> My intuition is that the changes make sense, but it would be nice if you
Simon> could describe the bugs in the commit message, to make sure we're on the
Simon> same page.
Tom> How's this?
[...]
Tom> Fix two bugs in gdbserver thread name handling
I'm checking in the updated version of this patch.
Tom
prev parent reply other threads:[~2024-01-09 14:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 14:59 Tom Tromey
2023-12-15 15:53 ` Simon Marchi
2023-12-15 16:24 ` Tom Tromey
2024-01-09 14:14 ` 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=87il42wq4y.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--cc=tromey@adacore.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).