From: Pedro Alves <palves@redhat.com>
To: Philippe Waroquiers <philippe.waroquiers@skynet.be>,
gdb-patches@sourceware.org
Subject: Re: [RFA] Improve on-line help for thread_apply_command and thread_apply_all_command.
Date: Fri, 20 Apr 2018 21:22:00 -0000 [thread overview]
Message-ID: <31be2d69-940f-9857-65af-91043167eae1@redhat.com> (raw)
In-Reply-To: <20180420211900.10064-1-philippe.waroquiers@skynet.be>
On 04/20/2018 10:19 PM, Philippe Waroquiers wrote:
> Add a Usage: line for thread_apply_command, in particular to mention
> the thread ID list.
>
> In thread_apply_command and thread_apply_all_command help, use
> uppercase for arg names, as this style seems to be more standard.
>
> 2018-04-20 Philippe Waroquiers <philippe.waroquiers@skynet.be>
>
> * thread.c (_initialize_thread): improve on-line help for
> thread_apply_command and thread_apply_all_command.
OK.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2018-04-20 21:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 21:19 Philippe Waroquiers
2018-04-20 21:22 ` Pedro Alves [this message]
2018-04-20 21:27 ` Philippe Waroquiers
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=31be2d69-940f-9857-65af-91043167eae1@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=philippe.waroquiers@skynet.be \
/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