From: Jonathan Nieder <jrnieder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jon Seymour <jon.seymour@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] Add --info-path and --man-path options to git.
Date: Sun, 1 May 2011 18:53:32 -0500 [thread overview]
Message-ID: <20110501235332.GD11550@elie> (raw)
In-Reply-To: <20110501234833.GC11550@elie>
Hi again,
Two quick corrections.
Jonathan Nieder wrote:
> So if "git gui" were to gain a
> documentation viewer widget instead of relying on git web--browse, it
> would need the HTML path.
Actually, it already uses the HTML path. :)
> So while I can't see the harm in exposing --info-path and --man-path,
> the current patch seems to do an incomplete job of documenting them.
> Perhaps this is about finding the documentation corresponding to a
> particular copy of git when a machine has multiple copies?
It seems Jon's and my mails crossed. Here's another use case for
--man-path: if your frontend wants to fall back to HTML documentation
without spawning a man pager when the manpages are not installed, it
needs to know where to look.
(See also gitgui-0.6.0~32, git-gui: Offer quick access to the HTML
formatted documentation, 2007-01-28)
next prev parent reply other threads:[~2011-05-01 23:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-01 8:16 [PATCH] Add --info-path and --man-path options to git Jon Seymour
2011-05-01 18:15 ` Junio C Hamano
2011-05-01 22:47 ` Jon Seymour
2011-05-01 23:48 ` Jonathan Nieder
2011-05-01 23:53 ` Jonathan Nieder [this message]
2011-05-02 0:02 ` Junio C Hamano
2011-05-02 0:06 ` Jon Seymour
2011-05-02 0:12 ` Jon Seymour
2011-05-02 0:25 ` Jonathan Nieder
2011-05-02 3:47 ` Junio C Hamano
2011-05-02 5:15 ` Jonathan Nieder
2011-05-02 6:07 ` [PATCH] Documentation: clarify meaning of --html-path, --man-path, and --info-path Jonathan Nieder
2011-05-02 6:49 ` Jon Seymour
2011-05-02 17:24 ` Junio C Hamano
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=20110501235332.GD11550@elie \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jon.seymour@gmail.com \
/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).