From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: "Pascal Obry" <pascal@obry.net>, "Xavier Maillard" <xma@gnu.org>,
=?iso-2022-jp?B?GyRCJDckaSQkJDckSiRKJDMbKEIs?=@a-sasl-fastnet.sasl.smtp.pobox.com,
git@vger.kernel.org
Subject: Re: [PATCH] help: warn if specified 'man.viewer' is unsupported, instead of erroring out
Date: Wed, 12 Mar 2008 23:22:09 -0700 [thread overview]
Message-ID: <7vzlt3ywha.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080313071040.bbf5528b.chriscool@tuxfamily.org> (Christian Couder's message of "Thu, 13 Mar 2008 07:10:40 +0100")
Christian Couder <chriscool@tuxfamily.org> writes:
> Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
> ---
> help.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> This was suggested by Xavier Maillard.
>
> diff --git a/help.c b/help.c
> index 5da8c9c..ecaca77 100644
> --- a/help.c
> +++ b/help.c
> @@ -139,7 +139,7 @@ static int add_man_viewer(const char *value)
> else if (!strcasecmp(value, "konqueror"))
> do_add_man_viewer(exec_man_konqueror);
> else
> - return error("'%s': unsupported man viewer.", value);
> + warning("'%s': unsupported man viewer.", value);
>
> return 0;
> }
While I'd agree this is a good change, the author should justify it in the
commit log message. I ask list regulars like you to set a good example
for others.
When a document viewer that is unknown to the current version of
git is specified in the .git/config file, instead of erroring out
the process completely, just issue a warning. It might be that
the user usually is using a newer git that supports it (and the
configuration is written for that version) but is temporarily
using an older git that does not know the viewer.
next prev parent reply other threads:[~2008-03-13 6:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 6:10 [PATCH] help: warn if specified 'man.viewer' is unsupported, instead of erroring out Christian Couder
2008-03-13 6:22 ` Junio C Hamano [this message]
2008-03-14 1:00 ` Xavier Maillard
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=7vzlt3ywha.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc==?iso-2022-jp?B?GyRCJDckaSQkJDckSiRKJDMbKEIs?=@a-sasl-fastnet.sasl.smtp.pobox.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=pascal@obry.net \
--cc=xma@gnu.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).