From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simon.marchi@efficios.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/4] Cleanups, remove get_exec_file
Date: Mon, 03 Jun 2024 08:53:49 -0600 [thread overview]
Message-ID: <87o78iqdqa.fsf@tromey.com> (raw)
In-Reply-To: <20240530185509.265901-1-simon.marchi@efficios.com> (Simon Marchi's message of "Thu, 30 May 2024 14:53:52 -0400")
>>>>> "Simon" == Simon Marchi <simon.marchi@efficios.com> writes:
Simon> Some cleanups and simplifications around getting the exec filename. No
Simon> behavior change intended.
This all looks reasonable to me.
Approved-By: Tom Tromey <tom@tromey.com>
Tom
next prev parent reply other threads:[~2024-06-03 14:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 18:53 Simon Marchi
2024-05-30 18:53 ` [PATCH 1/4] gdb: make progspace::exec_filename private, add getter / setter Simon Marchi
2024-05-30 18:53 ` [PATCH 2/4] gdb: replace `get_exec_file (0)` calls with `current_program_space->exec_filename ()` Simon Marchi
2024-05-30 18:53 ` [PATCH 3/4] gdb: remove dead code in nto-procfs.c Simon Marchi
2024-05-30 18:53 ` [PATCH 4/4] gdb: remove get_exec_file Simon Marchi
2024-06-03 14:53 ` Tom Tromey [this message]
2024-06-08 3:16 ` [PATCH 0/4] Cleanups, " 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=87o78iqdqa.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).