From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simon.marchi@efficios.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/2] Rename two structures
Date: Mon, 05 Feb 2024 13:34:25 -0700 [thread overview]
Message-ID: <87r0hqejla.fsf@tromey.com> (raw)
In-Reply-To: <20240205201954.122492-1-simon.marchi@efficios.com> (Simon Marchi's message of "Mon, 5 Feb 2024 15:18:32 -0500")
>>>>> "Simon" == Simon Marchi <simon.marchi@efficios.com> writes:
Simon> I'm currently doing changes in the solib area. I have these preparatory
Simon> patches that I think make sense on their own. They could be merged
Simon> right away to reduce the size of upcoming series.
These both seem fine to me.
Approved-By: Tom Tromey <tom@tromey.com>
Tom
next prev parent reply other threads:[~2024-02-05 20:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 20:18 Simon Marchi
2024-02-05 20:18 ` [PATCH 1/2] gdb: rename struct shobj -> struct solib Simon Marchi
2024-02-05 20:18 ` [PATCH 2/2] gdb: rename target_so_ops to solib_ops Simon Marchi
2024-02-05 20:34 ` Tom Tromey [this message]
2024-02-05 21:11 ` [PATCH 0/2] Rename two structures Simon Marchi
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=87r0hqejla.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).