From: Junio C Hamano <gitster@pobox.com>
To: Stefan Beller <sbeller@google.com>
Cc: Thomas Schneider <thosch97@gmail.com>,
"git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH] Documentation: Add target to build PDF manpages
Date: Fri, 20 Mar 2015 13:21:41 -0700 [thread overview]
Message-ID: <xmqq4mpfe7xm.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAGZ79ka7tPA17Y-vPPp5W_4-0UMnHMfM9+eQ8jc4eu23FpM2ug@mail.gmail.com> (Stefan Beller's message of "Fri, 20 Mar 2015 10:19:36 -0700")
Stefan Beller <sbeller@google.com> writes:
> ... though how would I read man pages in pdf
> format? I tried searching the web and all I can find is how
> to convert the a man page to pdf. So is there a conveniant
> way to tell `man` to prefer opening pdfs when available?
I presume that "man -Tpdf git.1" is not what you are looking for, as
that would literally be how you get the manpages in PDF format?
Personally, I honestly am not quite sure why anybody wants to
generate manpages in the PDF format like this patch does, unless
they are planning to print them on paper, in which case the existing
manpages (git.1 and friends) or html pages (git.html and friends)
should be an already available source format.
next prev parent reply other threads:[~2015-03-20 20:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 11:23 [PATCH] Documentation: Add target to build PDF manpages Thomas Schneider
2015-03-20 17:19 ` Stefan Beller
2015-03-20 19:32 ` Philip Oakley
2015-03-20 20:21 ` Junio C Hamano [this message]
2015-03-20 21:18 ` Thomas Schneider
2015-03-20 21:28 ` Junio C Hamano
2015-03-20 21:54 ` Thomas Schneider
2015-03-20 22:15 ` Philip Oakley
2015-03-20 22:19 ` Stefan Beller
2015-03-20 22:38 ` Junio C Hamano
2015-03-23 15:46 ` Michael J Gruber
2015-03-24 23:28 ` Philip Oakley
2015-03-25 11:43 ` Thomas Schneider
2015-03-20 22:42 ` 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=xmqq4mpfe7xm.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=sbeller@google.com \
--cc=thosch97@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.