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: Mon, 2 May 2011 00:15:07 -0500 [thread overview]
Message-ID: <20110502051507.GB14547@elie> (raw)
In-Reply-To: <7vzkn5pxv5.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> Where is your unhappiness coming from? Is this your argument?
>
> 'git help' allows distros' oversight with its -m and -i options;
> it discourages distros to get their act together.
No, my discomfort was not on behalf of distros. It wouldn't do
anything to help or hurt distros, since they would be installing to
/usr/share/man.
When I said "installers' mistakes", I specifically meant the user that
installs manual pages to ~/share/man without setting MANPATH to
include that. I agreed that that's an unfortunate thing to happen to
anybody, but I didn't think git is the right place to fix it. Because
it affects anyone else installing something to $HOME, and as a user I
wouldn't _expect_ git to fix it.
What my analysis was missing is that this is not only about the user
who runs "git help -m" as a fancy way of running "man git" and expects
it to work better (who I still have no sympathy for). It is much more
about the user who runs
git add --help
or chooses Help → Manual in her porcelain, who certainly deserves some
documentation whether her MANPATH is set correctly or not.
I also should have remembered v1.5.4-rc0~54 (Let git-help prefer
man-pages installed with this version of git, 2007-12-06), which is
about showing the manual in /opt/git-next/man in preference to a stale
manpage from /opt/git-master/man when running
"/opt/git-next/bin/git add --help".
So I was very confused indeed. Sorry to waste your time, and thanks
for setting me straight.
next prev parent reply other threads:[~2011-05-02 5:15 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
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 [this message]
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=20110502051507.GB14547@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).