public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-6880] gcov: Fix "subcomand" typos [PR109297] Date: Mon, 27 Mar 2023 12:49:53 +0000 (GMT) [thread overview] Message-ID: <20230327124953.E69FC3858D39@sourceware.org> (raw) https://gcc.gnu.org/g:cffa72fde8ce9c767e20c058892929d9c9b33ae7 commit r13-6880-gcffa72fde8ce9c767e20c058892929d9c9b33ae7 Author: Jonathan Wakely <jwakely@redhat.com> Date: Mon Mar 27 13:46:46 2023 +0100 gcov: Fix "subcomand" typos [PR109297] gcc/ChangeLog: PR gcov-profile/109297 * gcov-tool.cc (merge_usage): Fix "subcomand" typo. (merge_stream_usage): Likewise. (overlap_usage): Likewise. Diff: --- gcc/gcov-tool.cc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/gcc/gcov-tool.cc b/gcc/gcov-tool.cc index 88b7936a4f4..0140e7f2a4a 100644 --- a/gcc/gcov-tool.cc +++ b/gcc/gcov-tool.cc @@ -185,7 +185,7 @@ static const struct option merge_options[] = static void ATTRIBUTE_NORETURN merge_usage (void) { - fnotice (stderr, "Merge subcomand usage:"); + fnotice (stderr, "Merge subcommand usage:"); print_merge_usage_message (true); exit (FATAL_EXIT_CODE); } @@ -255,7 +255,7 @@ static const struct option merge_stream_options[] = static void ATTRIBUTE_NORETURN merge_stream_usage (void) { - fnotice (stderr, "Merge-stream subcomand usage:"); + fnotice (stderr, "Merge-stream subcommand usage:"); print_merge_stream_usage_message (true); exit (FATAL_EXIT_CODE); } @@ -507,7 +507,7 @@ static const struct option overlap_options[] = static void ATTRIBUTE_NORETURN overlap_usage (void) { - fnotice (stderr, "Overlap subcomand usage:"); + fnotice (stderr, "Overlap subcommand usage:"); print_overlap_usage_message (true); exit (FATAL_EXIT_CODE); }
reply other threads:[~2023-03-27 12:49 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230327124953.E69FC3858D39@sourceware.org \ --to=redi@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ /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: linkBe 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).