From: Michael J Gruber <git@drmicha.warpmail.net>
To: Matthieu Moy <Matthieu.Moy@imag.fr>
Cc: Miklos Vajna <vmiklos@frugalware.org>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: [PATCH] git-daemon documentation: use {tilde}
Date: Wed, 17 Dec 2008 10:07:15 +0100 [thread overview]
Message-ID: <4948C143.8030609@drmicha.warpmail.net> (raw)
In-Reply-To: <vpqbpvcro5z.fsf@bauges.imag.fr>
Matthieu Moy venit, vidit, dixit 16.12.2008 19:05:
> Michael J Gruber <git@drmicha.warpmail.net> writes:
>
>> Miklos Vajna venit, vidit, dixit 16.12.2008 16:48:
>>> Use '{tilde}' instead of '~', becase the later does not appear in the
>>> manpage version, just in the HTML one.
>> Curiously, "git help daemon" (which execs "man git-daemon") displays the
>> tilde but "man git-daemon" does not (nor does "konqueror
>> man:git-daemon"). Humh?
>
> You probably have two manpages because of two git installations. "man"
> will take the one in your manpath, and git will try to find the one
> corresponding to the version of git you actually launched.
You're right! I have current pages in ~/share/man/man? and older ones in
~/man/man?. I guess the latter is in the standard search path (I don't
have MANPATH set) but the former is not. I probably dumped a man-tarball
in the standard place back when I didn't know about quick-install-doc.
Now I'm just wondering why ~/share/man is the standard target for git
and ~/man in the standard man path, at least on (K)Ubuntu 7.10 at my
workplace.
Michael
prev parent reply other threads:[~2008-12-17 9:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 15:48 [PATCH] git-daemon documentation: use {tilde} Miklos Vajna
2008-12-16 17:38 ` Michael J Gruber
2008-12-16 17:50 ` Miklos Vajna
2008-12-16 18:05 ` Matthieu Moy
2008-12-17 9:07 ` Michael J Gruber [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=4948C143.8030609@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=Matthieu.Moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=vmiklos@frugalware.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).