From: Christian Couder <chriscool@tuxfamily.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Eric Wong <normalperson@yhbt.net>, git@vger.kernel.org
Subject: Re: [PATCH 1/2] Documentation: config: add "browser.<tool>.path".
Date: Tue, 29 Jan 2008 07:07:56 +0100 [thread overview]
Message-ID: <200801290707.57040.chriscool@tuxfamily.org> (raw)
In-Reply-To: <7v1w82wgev.fsf@gitster.siamese.dyndns.org>
Le lundi 28 janvier 2008, Junio C Hamano a écrit :
> Christian Couder <chriscool@tuxfamily.org> writes:
> >
> > +browser.<tool>.path::
> > + Override the path for the given tool that may be used to
> > + browse help. See linkgit:git-help[1].
> > +
>
> Thanks.
>
> I wonder if we want to stress the fact that this is about
> rendering HTML version of the manual. IOW, the <tool>.path
> is about the path the chosen HTML renderer program is at, and
> not consulted at all unless "git help -w help" is run.
>
> Also, do we want to list the repertoire of <tool>? Unlike
> <name> in "remote.<name>.url" and "branch.<name>.remote", this
> is not something the end user can arbitrarily name.
>
> Incidentally, I notice that git-help manual page does not list
> what browsers are supported (except that it hints that firefox
> is usable by having an example "browser.firefox.path"), even
> though it tells how the browser is picked via "*.browser".
It should be fixed in the following patch series.
Thanks,
Christian.
prev parent reply other threads:[~2008-01-29 6:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 7:02 [PATCH 1/2] Documentation: config: add "browser.<tool>.path" Christian Couder
2008-01-28 7:36 ` Junio C Hamano
2008-01-29 6:07 ` Christian Couder [this message]
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=200801290707.57040.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=normalperson@yhbt.net \
/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).