From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Jim Davis <jim.epost@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>, Daniel Vetter <daniel@ffwll.ch>,
linux-doc <linux-doc@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH 0/5] Make PDF builds work again
Date: Thu, 6 Jul 2017 06:54:15 -0300 [thread overview]
Message-ID: <20170706065415.0fb1aca9@vento.lan> (raw)
In-Reply-To: <CA+r1Zhg=5sd6qvW=dVvg0SOhEfMQmYvTMhFyLniCbZLuTke-6A@mail.gmail.com>
Em Wed, 5 Jul 2017 14:22:35 -0700
Jim Davis <jim.epost@gmail.com> escreveu:
> On Mon, Jul 3, 2017 at 5:44 AM, Jonathan Corbet <corbet@lwn.net> wrote:
> > On Mon, 3 Jul 2017 10:25:38 +0200
> > Daniel Vetter <daniel@ffwll.ch> wrote:
> >
> >> Only now stumbled over the full thread, but the drm patch is already
> >> queued up for at least 4.13 (Dave was out and all that). I guess we could
> >> try to cherry-pick through stable.
> >
> > I kind of gave up on the 4.12 goal, at least for now. The number of
> > complaints has not been huge - I suspect you're far from the only one who
> > is not too worried about building PDFs...:)
>
> If fixing pdf (and ps) builds isn't worth the bother -- which I
> wouldn't debate -- then it's best to just drop those build targets.
> The only worrisome thing I see here is having build targets carried
> from release to release that don't work.
My $5 cents on that. We do automatic pdf builds at linuxtv.org
since when we moved the media books to Sphinx. In order to avoid
regressions, we use a virtual environment for Sphinx, and we only
update to a newer version after checking if the upgrade won't break
build. Currently, it is running Sphinx version 1.4.9.
I did a grep on the access for the media.pdf doc at the apache's
log. We don't keep a long history there.
We had 41 accesses to the pdf logs over the last ~3 days, with means
that people are finding PDF output useful.
-
>From my side, I like having everything into a single file
specially when I'm needing to find things at the document. Well,
ePub sort of provides that, but it is a way worse than PDF or
html, specially when big tables are there. Btw, over the
last ~3 days, we had only 1 access to the ePub version. So, not a
very popular format.
Thanks,
Mauro
next prev parent reply other threads:[~2017-07-06 9:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-18 23:46 [PATCH 0/5] Make PDF builds work again Jonathan Corbet
2017-06-18 23:46 ` [PATCH 1/5] Docs: Include the Latex "ifthen" package Jonathan Corbet
2017-06-18 23:46 ` [PATCH 2/5] Docs: Remove redundant geometry package inclusion Jonathan Corbet
2017-06-19 10:30 ` Mauro Carvalho Chehab
2017-06-19 10:49 ` Mauro Carvalho Chehab
2017-06-23 19:39 ` Jonathan Corbet
2017-06-23 21:26 ` Mauro Carvalho Chehab
2017-06-18 23:46 ` [PATCH 3/5] Docs: fix table problems in ras.rst Jonathan Corbet
2017-06-18 23:46 ` [PATCH 4/5] Docs: Use kernel-figure in vidioc-g-selection.rst Jonathan Corbet
2017-06-18 23:46 ` [PATCH 5/5] DRM: Fix an incorrectly formatted table Jonathan Corbet
2017-06-18 23:48 ` [PATCH 0/5] Make PDF builds work again Jonathan Corbet
2017-06-19 1:18 ` Mauro Carvalho Chehab
2017-06-19 14:43 ` Mauro Carvalho Chehab
2017-07-03 8:25 ` Daniel Vetter
2017-07-03 12:44 ` Jonathan Corbet
2017-07-05 21:22 ` Jim Davis
2017-07-06 8:28 ` Markus Heiser
2017-07-06 9:54 ` Mauro Carvalho Chehab [this message]
2017-07-05 20:03 ` Frank Rowand
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=20170706065415.0fb1aca9@vento.lan \
--to=mchehab@s-opensource.com \
--cc=corbet@lwn.net \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--cc=jim.epost@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 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.