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 15:38:27 -0700 [thread overview]
Message-ID: <xmqqmw37cn18.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAGZ79kaDnRiUQ6=3gVvsPrkSzkNbACRvgQBSo8gmpRZ8bka84g@mail.gmail.com> (Stefan Beller's message of "Fri, 20 Mar 2015 15:19:04 -0700")
Stefan Beller <sbeller@google•com> writes:
> Thomas referencing reading the man page offline, made me wonder
> why you wouldn't read the man pages itself as they can also be
> carried around offline. But the striking point is "on an iPad", which
> doesn't offer you the convenience of a shell etc, but pdf is fine to read
> there. Also you can add comments to pdfs more easily that html pages
> I'd guess.
>
> So the patch makes sense to me now. It's just a use case I'm personally
> not interested in for now, but I don't oppose it as is.
Well, my comment was not about opposing to it, but was about
questioning the usefulness of it, iow, who would
benefit from having this patch in my tree?
I didn't see (and I still do not quite see) why people would want to
have separate pdf files for all the subcommands (instead of say an
.epub or .pdf that binds all the man pages and perhaps user-manual,
just like we do for .texi/.info).
next prev parent reply other threads:[~2015-03-20 22:38 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
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 [this message]
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=xmqqmw37cn18.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