From: Miklos Vajna <vmiklos@frugalware.org>
To: Leo Razoumov <slonik.az@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [RFC/PATCH] Add support for a pdf version of the user manual
Date: Thu, 11 Dec 2008 01:35:57 +0100 [thread overview]
Message-ID: <20081211003557.GS5691@genesis.frugalware.org> (raw)
In-Reply-To: <ee2a733e0812101620s5fc2ff27p81826a5ff827e154@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]
On Wed, Dec 10, 2008 at 07:20:42PM -0500, Leo Razoumov <slonik.az@gmail.com> wrote:
> On 12/10/08, Junio C Hamano <gitster@pobox.com> wrote:
> > "Leo Razoumov" <slonik.az@gmail.com> writes:
> >
> > > BTW, for those of us without dblatex, is it possible to have pdf
> > > manual pregenerated the same way html and man pages are pregenerated
> > > for official releases in the git repo?
> >
> >
> > Those of us includes myself, so...
>
> Ouch:-) Does it mean that such a useful patch has a low probability of
> being accepted?
First, just like the info pages, I don't think it's a problem at all if
the autogenerated pdf version is not part of git.git. I sent the patch
to provide an easy way to do the pdf generation, not to request the
autobuild of it as well.
Second, I think the autogeneration for pdf should not be done similar to
the man/html versions, as the pdf itself is 421K.
However, I'm happy to set up a nightly cron job to build the pdf in case
master is updated and/or there is a new release - in case there is
demand for that.
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-12-11 0:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-10 22:44 [RFC/PATCH] Add support for a pdf version of the user manual Miklos Vajna
2008-12-11 0:06 ` Leo Razoumov
2008-12-11 0:11 ` Junio C Hamano
2008-12-11 0:20 ` Leo Razoumov
2008-12-11 0:35 ` Miklos Vajna [this message]
2008-12-11 0:37 ` 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=20081211003557.GS5691@genesis.frugalware.org \
--to=vmiklos@frugalware.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=slonik.az@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).