From: Jakub Jelinek <jakub@redhat.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: [committed] gcov-tool: Use subcommand rather than sub-command in function comments
Date: Tue, 28 Mar 2023 11:56:14 +0200 [thread overview]
Message-ID: <ZCK5vnMKxCV6UIXw@tucnak> (raw)
In-Reply-To: <20230327125049.967747-1-jwakely@redhat.com>
Hi!
Follow-up to the recently committed fix of fixing the "subcomand" typos
in diagnostics.
Committed to trunk as obvious.
2023-03-28 Jakub Jelinek <jakub@redhat.com>
Jonathan Wakely <jwakely@redhat.com>
* gcov-tool.cc (do_merge, do_merge_stream, do_rewrite, do_overlap):
Use subcommand rather than sub-command in function comments.
--- gcc/gcov-tool.cc.jj 2023-03-28 10:26:23.579047495 +0200
+++ gcc/gcov-tool.cc 2023-03-28 11:51:27.545112038 +0200
@@ -190,7 +190,7 @@ merge_usage (void)
exit (FATAL_EXIT_CODE);
}
-/* Driver for profile merge sub-command. */
+/* Driver for profile merge subcommand. */
static int
do_merge (int argc, char **argv)
@@ -260,7 +260,7 @@ merge_stream_usage (void)
exit (FATAL_EXIT_CODE);
}
-/* Driver for profile merge-stream sub-command. */
+/* Driver for profile merge-stream subcommand. */
static int
do_merge_stream (int argc, char **argv)
@@ -358,7 +358,7 @@ rewrite_usage (void)
exit (FATAL_EXIT_CODE);
}
-/* Driver for profile rewrite sub-command. */
+/* Driver for profile rewrite subcommand. */
static int
do_rewrite (int argc, char **argv)
@@ -518,7 +518,7 @@ int overlap_hot_only;
int overlap_use_fullname;
double overlap_hot_threshold = 0.005;
-/* Driver for profile overlap sub-command. */
+/* Driver for profile overlap subcommand. */
static int
do_overlap (int argc, char **argv)
Jakub
prev parent reply other threads:[~2023-03-28 9:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 12:50 [committed] gcov: Fix "subcomand" typos [PR109297] Jonathan Wakely
2023-03-28 9:56 ` Jakub Jelinek [this message]
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=ZCK5vnMKxCV6UIXw@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).