Re: [PATCH] standardize usage strings that were missed the first time
Alex Henrie <alexhenrie24@gmail.com> writes:
> This is a follow-up to commit 9c9b4f2f8b7f27f3984e80d053106d5d41cbb03b.
Please do not force the reader to type "git show 9c9b4f2".
Show 33 quoted lines
>
> Signed-off-by: Alex Henrie <alexhenrie24@gmail.com>
> ---
> builtin/blame.c | 2 +-
> builtin/log.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/builtin/blame.c b/builtin/blame.c
> index 06484c2..0b2f4ed 100644
> --- a/builtin/blame.c
> +++ b/builtin/blame.c
> @@ -27,7 +27,7 @@
> #include "line-range.h"
> #include "line-log.h"
>
> -static char blame_usage[] = N_("git blame [<options>] [<rev-opts>] [<rev>] [--] file");
> +static char blame_usage[] = N_("git blame [<options>] [<rev-opts>] [<rev>] [--] <file>");
>
> static const char *blame_opt_usage[] = {
> blame_usage,
> diff --git a/builtin/log.c b/builtin/log.c
> index dd8f3fc..4c4e6be 100644
> --- a/builtin/log.c
> +++ b/builtin/log.c
> @@ -38,7 +38,7 @@ static const char *fmt_patch_subject_prefix = "PATCH";
> static const char *fmt_pretty;
>
> static const char * const builtin_log_usage[] = {
> - N_("git log [<options>] [<revision range>] [[--] <path>...]"),
> + N_("git log [<options>] [<revision-range>] [[--] <path>...]"),
> N_("git show [<options>] <object>..."),
> NULL
> };