From: Simon Marchi <simark@simark.ca>
To: "Aktemur, Tankut Baris" <tankut.baris.aktemur@intel.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] gdb/thread: fine-tune 'info threads' help text
Date: Mon, 19 Oct 2020 11:59:47 -0400 [thread overview]
Message-ID: <54151150-695a-00c1-04b2-fd396f272307@simark.ca> (raw)
In-Reply-To: <SN6PR11MB2893C35C5DBB58972E0B233EC41E0@SN6PR11MB2893.namprd11.prod.outlook.com>
On 2020-10-19 11:57 a.m., Aktemur, Tankut Baris via Gdb-patches wrote:
> I agree, but I checked some other arbitrary commands manually, and also did a
> `grep -A 1 "Usage:" *.c`, and found that a great portion of commands do not print that
> separator newline. For consistency, let me push without the newline.
Ok.
Simon
next prev parent reply other threads:[~2020-10-19 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 15:32 Tankut Baris Aktemur via Gdb-patches
2020-10-19 15:39 ` Simon Marchi
2020-10-19 15:57 ` Aktemur, Tankut Baris via Gdb-patches
2020-10-19 15:59 ` Simon Marchi [this message]
2020-10-19 18:51 ` Philippe Waroquiers via Gdb-patches
2020-10-19 16:04 ` Eli Zaretskii via Gdb-patches
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=54151150-695a-00c1-04b2-fd396f272307@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=tankut.baris.aktemur@intel.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