From: Junio C Hamano <gitster@pobox.com>
To: Pat Thoyts <patthoyts@users.sourceforge.net>
Cc: git@vger.kernel.org, Vincent van Ravesteijn <vfr@lyx.org>
Subject: Re: [PATCH] Restore use of 'help.format' configuration property in 'git help'
Date: Fri, 22 Jun 2012 11:06:29 -0700 [thread overview]
Message-ID: <7vy5nfp6fu.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1340369326-1840-1-git-send-email-patthoyts@users.sourceforge.net> (Pat Thoyts's message of "Fri, 22 Jun 2012 13:48:46 +0100")
Pat Thoyts <patthoyts@users.sourceforge.net> writes:
> Commit 1cc8af0 "help: use HTML as the default help format on Windows"
> lost the ability to make use of the help.format config value by forcing
> the use of a compiled in default if no command-line argument was provided.
> This commit restores the use of the help.format value if one is
> available, overriding the compiled default.
Of course. Sorry for not catching it earlier.
>
> Signed-off-by: Pat Thoyts <patthoyts@users.sourceforge.net>
> ---
> builtin/help.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/builtin/help.c b/builtin/help.c
> index 536d4fd..8f9cd60 100644
> --- a/builtin/help.c
> +++ b/builtin/help.c
> @@ -449,10 +449,10 @@ int cmd_help(int argc, const char **argv, const char *prefix)
> setup_git_directory_gently(&nongit);
> git_config(git_help_config, NULL);
>
> - if (parsed_help_format == HELP_FORMAT_NONE)
> - help_format = parse_help_format(DEFAULT_HELP_FORMAT);
> - else
> + if (parsed_help_format != HELP_FORMAT_NONE)
> help_format = parsed_help_format;
> + if (help_format == HELP_FORMAT_NONE)
> + help_format = parse_help_format(DEFAULT_HELP_FORMAT);
>
> alias = alias_lookup(argv[0]);
> if (alias && !is_git_command(argv[0])) {
next prev parent reply other threads:[~2012-06-22 18:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 12:48 [PATCH] Restore use of 'help.format' configuration property in 'git help' Pat Thoyts
2012-06-22 18:06 ` Junio C Hamano [this message]
2012-06-23 12:52 ` Vincent van Ravesteijn
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=7vy5nfp6fu.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=patthoyts@users.sourceforge.net \
--cc=vfr@lyx.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: link
Be 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 NNTP newsgroup(s).