From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simark@simark.ca>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 2/3] Use GNU style for metasyntactic variables in gdb
Date: Sun, 16 Sep 2018 12:13:00 -0000 [thread overview]
Message-ID: <877ejlr665.fsf@tromey.com> (raw)
In-Reply-To: <1f40ea99-e324-eb58-9049-4063f0204bc9@simark.ca> (Simon Marchi's message of "Sat, 15 Sep 2018 23:16:59 -0400")
>>>>> "Simon" == Simon Marchi <simark@simark.ca> writes:
Simon> On 2018-09-14 10:55 p.m., Tom Tromey wrote:
>> I searched for other spots that did not use the GNU style for
>> metasyntactic syntactic variables. This patch fixes most of the ones
>> I found in gdb proper. There are a few remaining in MI, but I was
>> unsure whether those should be touched.
Simon> LGTM.
Simon> Out of curiosity, is there a place in the GNU coding standard that explicitly
Simon> explains this?
Well, I thought so. Maybe there was in the past and it was removed?
Or maybe it needs to be added, because it is definitely a GNU
convention. You can see it in the --help of any GNU program. Maybe
this is one of those things that François Pinard was planning to put in
the proposed Gnits manual that we never wrote. I sent a note to
bug-standards.
Anyway I could only find a mention in the Texinfo manual, in the @var
node.
Tom
next prev parent reply other threads:[~2018-09-16 12:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-15 2:55 [PATCH 0/3] More use of GNU-style metasyntactic variables Tom Tromey
2018-09-15 2:55 ` [PATCH 1/3] Expand "show disassembler-options" output Tom Tromey
2018-09-16 3:12 ` Simon Marchi
2018-09-16 12:18 ` Tom Tromey
2018-09-15 2:55 ` [PATCH 3/3] Use GNU style for metasyntactic variables in gdbserver Tom Tromey
2018-09-16 3:17 ` Simon Marchi
2018-09-15 2:55 ` [PATCH 2/3] Use GNU style for metasyntactic variables in gdb Tom Tromey
2018-09-16 3:17 ` Simon Marchi
2018-09-16 12:13 ` Tom Tromey [this message]
2018-09-16 3:20 ` Simon Marchi
2018-09-16 12:16 ` Tom Tromey
2018-09-16 12:42 ` Tom Tromey
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=877ejlr665.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.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