From: Jonathan Corbet <corbet@lwn.net>
To: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/6] Better document Sphinx install instructions
Date: Mon, 17 Jul 2017 15:26:33 -0600 [thread overview]
Message-ID: <20170717152633.5cdeff38@lwn.net> (raw)
In-Reply-To: <20170717182305.4dfacc21@vento.lan>
On Mon, 17 Jul 2017 18:23:05 -0300
Mauro Carvalho Chehab <mchehab@s-opensource.com> wrote:
> Btw, I'm submitting in a few a second version of the patches with
> add a script to check Sphinx dependencies.
I figured I wasn't going to look at that until you get up to v42 or so -
maybe another day or two...? :)
jon
next prev parent reply other threads:[~2017-07-17 21:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-14 16:41 [PATCH v2 0/6] Better document Sphinx install instructions Mauro Carvalho Chehab
2017-07-14 16:41 ` [PATCH v2 1/6] changes.rst: Update Sphinx minimal requirements Mauro Carvalho Chehab
2017-07-14 16:41 ` [PATCH v2 2/6] docs-rst: move Sphinx install instructions to sphinx.rst Mauro Carvalho Chehab
2017-07-14 16:41 ` [PATCH v2 3/6] sphinx.rst: explain the usage of virtual environment Mauro Carvalho Chehab
2017-07-14 16:41 ` [PATCH v2 4/6] sphinx.rst: fix unknown reference Mauro Carvalho Chehab
2017-07-14 16:41 ` [PATCH v2 5/6] sphinx.rst: describe the install requirements for kfigure Mauro Carvalho Chehab
2017-07-14 16:41 ` [PATCH v2 6/6] sphinx.rst: better organize the documentation about PDF build Mauro Carvalho Chehab
2017-07-17 19:40 ` [PATCH v2 0/6] Better document Sphinx install instructions Jonathan Corbet
2017-07-17 21:23 ` Mauro Carvalho Chehab
2017-07-17 21:26 ` Jonathan Corbet [this message]
2017-07-17 21:55 ` Mauro Carvalho Chehab
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=20170717152633.5cdeff38@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=mchehab@s-opensource.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.