blame, log: format usage strings similarly to those in documentation
Earlier, 9c9b4f2f (standardize usage info string format, 2015-01-13) tried to make usage-string in line with the documentation by - Placing angle brackets around fill-in-the-blank parameters - Putting dashes in multiword parameter names - Adding spaces to [-f|--foobar] to make [-f | --foobar] - Replacing <foobar>* with [<foobar>...] but it missed a few places. Signed-off-by: Alex Henrie <alexhenrie24@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Alex Henrie committed
Apr 2, 2015 at 15:26 UTC
ce41720cad79d858f09ebfc88cf84a4b152645c7
2 files changed
+2
-2
builtin/blame.c
+1
-1
@@ -27,7 +27,7 @@
27
#include "line-range.h"
28
#include "line-log.h"
29
30
-static char blame_usage[] = N_("git blame [<options>] [<rev-opts>] [<rev>] [--] file");
30
+static char blame_usage[] = N_("git blame [<options>] [<rev-opts>] [<rev>] [--] <file>");
31
32
static const char *blame_opt_usage[] = {
33
blame_usage,
builtin/log.c
+1
-1
@@ -38,7 +38,7 @@ static const char *fmt_patch_subject_prefix = "PATCH";
38
static const char *fmt_pretty;
39
40
static const char * const builtin_log_usage[] = {
41
- N_("git log [<options>] [<revision range>] [[--] <path>...]"),
41
+ N_("git log [<options>] [<revision-range>] [[--] <path>...]"),
42
N_("git show [<options>] <object>..."),
43
NULL
44
};