From: Simon Marchi <simon.marchi@polymtl.ca>
To: Aaron Merey <amerey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] gdb: add set/show commands for managing debuginfod
Date: Fri, 29 Oct 2021 21:54:02 -0400 [thread overview]
Message-ID: <b34f6e5f-1ff4-32e7-2020-062e7b9e13f8@polymtl.ca> (raw)
In-Reply-To: <CAJDtP-TvZ4c32QkE0a-Q5t-x2GDacE2w81gvwekq4iUbUhnS7Q@mail.gmail.com>
On 2021-10-29 21:09, Aaron Merey wrote:
> Changed to use add_setshow_prefix_cmd. Because this function
> doesn't have a parameter for a custom show function I added
> a 'show debuginfod status' command so that the user can check
> whether debuginfod is set to 'on', 'off' or 'ask'.
Ah, I had not realized that, sorry. Well, you could have left it
as-is then :/.
Simon
next prev parent reply other threads:[~2021-10-30 1:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 23:01 [PATCH 0/2 v3] gdb: Add debuginfod first-use notification Aaron Merey
2021-10-18 23:01 ` [PATCH 1/2] gdb: add set/show commands for managing debuginfod Aaron Merey
2021-10-20 20:34 ` Keith Seitz
2021-10-21 22:23 ` Lancelot SIX
2021-10-25 22:30 ` Aaron Merey
2021-10-21 22:02 ` Lancelot SIX
2021-10-26 16:08 ` Simon Marchi
2021-10-28 22:18 ` Aaron Merey
2021-10-29 1:47 ` Simon Marchi
2021-10-30 1:09 ` Aaron Merey
2021-10-30 1:54 ` Simon Marchi [this message]
2021-10-31 2:43 ` Simon Marchi
2021-11-01 15:52 ` Simon Marchi
2021-11-01 17:39 ` Aaron Merey
2021-11-01 18:00 ` Simon Marchi
2021-11-02 16:51 ` Simon Marchi
2021-11-02 20:35 ` Aaron Merey
2021-10-18 23:01 ` [PATCH 2/2] gdb.texinfo: Expand documentation for debuginfod Aaron Merey
2021-10-19 11:17 ` Eli Zaretskii
2021-10-19 22:35 ` Aaron Merey
2021-10-20 11:38 ` Eli Zaretskii
2021-10-30 1:18 ` Aaron Merey
2021-10-30 6:57 ` Tom de Vries
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=b34f6e5f-1ff4-32e7-2020-062e7b9e13f8@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=amerey@redhat.com \
--cc=gdb-patches@sourceware.org \
/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).