Philip Oakley <philipoak...@iee.org> writes:
> Prepare for the addition of the -g --guides option to git help
> and show that help is available for both concept guides, and commands.
>
> Signed-off-by: Philip Oakley <philipoak...@iee.org>
> ---
This should come at the end after you taught the "-g" option, I
think. If we stopped with 1/5, then the message will promise "git
help -g" does something useful, while the code is not yet ready.
> git.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/git.c b/git.c
> index 39ba6b1..2f8aa41 100644
> --- a/git.c
> +++ b/git.c
> @@ -13,7 +13,9 @@ const char git_usage_string[] =
> " <command> [<args>]";
>
> const char git_more_info_string[] =
> - N_("See 'git help <command>' for more information on a specific
> command.");
> + N_("'git help -a' and 'git help -g' lists available subcommands and
> some\n"
> + "concept guides. See 'git help <command>' or 'git help <concept>'\n"
> + "to read about a specific subcommand or concept.");
>
> static struct startup_info git_startup_info;
> static int use_pager = -1;
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
