From: Junio C Hamano <gitster@pobox•com>
To: Thomas Schneider <thosch97@gmail•com>
Cc: Stefan Beller <sbeller@google•com>,
"git\@vger.kernel.org" <git@vger•kernel.org>
Subject: Re: [PATCH] Documentation: Add target to build PDF manpages
Date: Fri, 20 Mar 2015 14:28:34 -0700 [thread overview]
Message-ID: <xmqqzj77cq9p.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAJUTLVUK4+OiS_LDaFsRo_pwxF4nO2vR0zyumHBxBc9+8C3FUw@mail.gmail.com> (Thomas Schneider's message of "Fri, 20 Mar 2015 22:18:25 +0100")
Thomas Schneider <thosch97@gmail•com> writes:
>> 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.
> Somebody in the #git IRC channel...
> ... So, maybe most people are fine with the other formats, but those who
> need PDF can directly generate them.
I think you misunderstood me. I am not dismissing the need for PDF;
I am just saying that there is no need to directly generate them
from asciidoc sources, especially when there are already manpages
and html pages available as source to "print" to PDF.
next prev parent reply other threads:[~2015-03-20 21:28 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
2015-03-20 21:18 ` Thomas Schneider
2015-03-20 21:28 ` Junio C Hamano [this message]
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=xmqqzj77cq9p.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=sbeller@google$(echo .)com \
--cc=thosch97@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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