From: "John Cai via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: John Cai <johncai86@gmail.com>, John Cai <johncai86@gmail.com>
Subject: [PATCH] name-rev: replace --stdin with --annotate-stdin in synopsis
Date: Tue, 15 Feb 2022 20:52:07 +0000 [thread overview]
Message-ID: <pull.1216.git.git.1644958327302.gitgitgadget@gmail.com> (raw)
From: John Cai <johncai86@gmail.com>
d9976b184596 added --annotate-stdin to replace --stdin as a clearer flag
name. Since --stdin is to be deprecated, we should replace --stdin in
the synopsis.
Signed-off-by: John Cai <johncai86@gmail.com>
---
name-rev: replace --stdin with --annotate-stdin in synopsis
There was an oversight when we added --annotate-stdin to
git-name-rev(1). This patch corrects it by making the appropriate change
in the synopsis of git-name-rev(1)
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1216%2Fjohn-cai%2Fjc-update-name-rev-synopsis-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1216/john-cai/jc-update-name-rev-synopsis-v1
Pull-Request: https://github.com/git/git/pull/1216
builtin/name-rev.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/builtin/name-rev.c b/builtin/name-rev.c
index 138e3c30a2b..929591269dd 100644
--- a/builtin/name-rev.c
+++ b/builtin/name-rev.c
@@ -473,7 +473,7 @@ static void show_name(const struct object *obj,
static char const * const name_rev_usage[] = {
N_("git name-rev [<options>] <commit>..."),
N_("git name-rev [<options>] --all"),
- N_("git name-rev [<options>] --stdin"),
+ N_("git name-rev [<options>] --annotate-stdin"),
NULL
};
base-commit: b80121027d1247a0754b3cc46897fee75c050b44
--
gitgitgadget
next reply other threads:[~2022-02-15 20:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 20:52 John Cai via GitGitGadget [this message]
2022-02-16 1:40 ` [PATCH] name-rev: replace --stdin with --annotate-stdin in synopsis Junio C Hamano
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=pull.1216.git.git.1644958327302.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=johncai86@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.