From: Eli Zaretskii <eliz@gnu.org>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 1/2] gdb: merge solib-frv aix-solib debug options into "set/show debug solib"
Date: Mon, 28 Nov 2022 20:38:46 +0200 [thread overview]
Message-ID: <83r0xmncuh.fsf@gnu.org> (raw)
In-Reply-To: <26f7b567-98d1-9b55-622b-fa882de6fa8c@polymtl.ca> (message from Simon Marchi on Mon, 28 Nov 2022 13:29:54 -0500)
> Date: Mon, 28 Nov 2022 13:29:54 -0500
> Cc: gdb-patches@sourceware.org
> From: Simon Marchi <simon.marchi@polymtl.ca>
>
> Given I see them as maintenance commands, I'd rather not add aliases,
> unless you have strong feelings about it.
If everyone else is fine with the deletion, I'm fine as well.
Thanks.
next prev parent reply other threads:[~2022-11-28 18:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 17:00 Simon Marchi
2022-11-28 17:00 ` [PATCH v2 2/2] gdb: add some debug statements to solib-svr4.c Simon Marchi
2022-11-28 17:24 ` [PATCH v2 1/2] gdb: merge solib-frv aix-solib debug options into "set/show debug solib" Eli Zaretskii
2022-11-28 18:29 ` Simon Marchi
2022-11-28 18:38 ` Eli Zaretskii [this message]
2022-12-02 19:44 ` 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=83r0xmncuh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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).