From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Markus Heiser <markus.heiser@darmarit.de>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH 3/5] sphinx-pre-install: use a requirements file
Date: Mon, 17 Jul 2017 06:36:40 -0300 [thread overview]
Message-ID: <20170717063640.4da88f97@vento.lan> (raw)
In-Reply-To: <1D7A6D39-CCF0-45D2-AE8A-B7E186ADB371@darmarit.de>
Em Mon, 17 Jul 2017 08:00:07 +0200
Markus Heiser <markus.heiser@darmarit.de> escreveu:
> > Am 17.07.2017 um 00:08 schrieb Mauro Carvalho Chehab <mchehab@s-opensource.com>:
> >
> > Instead of using 3 commands to install a virtualenv, use
> > a single one, reading the requirements from this file:
> >
> > Documentation/sphinx/requirements.txt
> >
> > Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
>
> Hi Mauro,
>
> I get a ..
>
> fatal: sha1 information is lacking or useless (Documentation/doc-guide/sphinx.rst)
>
> and I miss the Documentation/doc-guide/sphinx.rst file in this patch.
>
> Did it only happened to me?
Sorry, I forgot to mention. This patch depends on the patch series I
posted before adding information about the Sphinx install procedures:
[PATCH v2 0/6] Better document Sphinx install instructions
https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1444295.html
Thanks,
Mauro
next prev parent reply other threads:[~2017-07-17 9:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-16 22:08 [PATCH 0/5] Add a script to check for Sphinx install requirements Mauro Carvalho Chehab
2017-07-16 22:08 ` [PATCH 1/5] scripts/sphinx-pre-install: add a script to check Sphinx install Mauro Carvalho Chehab
2017-07-16 22:08 ` [PATCH 2/5] sphinx-pre-install: detect an existing virtualenv Mauro Carvalho Chehab
2017-07-16 22:08 ` [PATCH 3/5] sphinx-pre-install: use a requirements file Mauro Carvalho Chehab
2017-07-17 6:00 ` Markus Heiser
2017-07-17 9:36 ` Mauro Carvalho Chehab [this message]
2017-07-16 22:08 ` [PATCH 4/5] sphinx.rst: document scripts/sphinx-pre-install script Mauro Carvalho Chehab
2017-07-16 22:08 ` [PATCH 5/5] doc: Makefile: if sphinx is not found, run a check script Mauro Carvalho Chehab
2017-07-17 8:15 ` [PATCH 0/5] Add a script to check for Sphinx install requirements Markus Heiser
2017-07-17 9:33 ` Mauro Carvalho Chehab
2017-07-17 10:09 ` Mauro Carvalho Chehab
2017-07-17 10:32 ` Markus Heiser
2017-07-17 10:57 ` Mauro Carvalho Chehab
2017-07-18 8:53 ` Markus Heiser
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=20170717063640.4da88f97@vento.lan \
--to=mchehab@s-opensource.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.heiser@darmarit.de \
--cc=mchehab@infradead.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.