From: Pedro Alves <palves@redhat.com>
To: Philippe Waroquiers <philippe.waroquiers@skynet.be>,
gdb-patches@sourceware.org
Subject: Re: [RFA] Make first and last lines of 'command help documentation' consistent.
Date: Thu, 11 Jul 2019 14:18:00 -0000 [thread overview]
Message-ID: <35830d90-8110-4279-4553-bc540ecc9064@redhat.com> (raw)
In-Reply-To: <20190616195804.9427-1-philippe.waroquiers@skynet.be>
On 6/16/19 8:58 PM, Philippe Waroquiers wrote:
> add_cmd ("substitute-path", class_files, set_substitute_path_command,
> _("\
> +Add a substitution rule to rewrite source files names directories.\n\
"files names directories" reads a bit ood, seems like a plural too many
somewhere.
Maybe you're missing a possessive apostrophe, like:
Add a substitution rule to rewrite source files names' directories.
> Usage: set substitute-path FROM TO\n\
> Add a substitution rule replacing FROM into TO in source file names.\n\
This sentence here looks a little redundant now.
> If a substitution rule was previously set for FROM, the old rule\n\
> @@ -1938,6 +1939,7 @@ is replaced by the new one."),
>
> add_cmd ("substitute-path", class_files, unset_substitute_path_command,
> _("\
> +Delete one or all substitution rules rewriting source files names directories.\n\
Ditto.
> Usage: unset substitute-path [FROM]\n\
--
Thanks,
Pedro Alves
next prev parent reply other threads:[~2019-07-11 14:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-16 19:58 Philippe Waroquiers
2019-07-05 20:04 ` PING " Philippe Waroquiers
2019-07-10 17:02 ` Tom Tromey
2019-07-10 22:31 ` Philippe Waroquiers
2019-07-11 12:22 ` Tom Tromey
2019-07-11 12:53 ` Pedro Alves
2019-07-11 13:12 ` Tom Tromey
2019-07-11 15:49 ` Pedro Alves
2019-07-11 15:51 ` Pedro Alves
2019-07-11 15:58 ` Tom Tromey
2019-07-11 15:44 ` Pedro Alves
2019-07-11 13:49 ` Pedro Alves
2019-07-29 21:27 ` Philippe Waroquiers
2019-07-11 14:18 ` Pedro Alves [this message]
2019-07-11 15:39 ` Pedro Alves
2019-07-11 15:43 ` Pedro Alves
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=35830d90-8110-4279-4553-bc540ecc9064@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