From: Markus Heiser <markus.heiser@darmarit.de>
To: "Tobin C. Harding" <tobin@kernel.org>, Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/9] docs: Fix various build warnings/errors
Date: Fri, 8 Mar 2019 09:40:03 +0100 [thread overview]
Message-ID: <2b5f55e5-79d6-2538-5054-b34e4b93e721@darmarit.de> (raw)
In-Reply-To: <20190307211153.28400-1-tobin@kernel.org>
Am 07.03.19 um 22:11 schrieb Tobin C. Harding:
> Hi,
>
> I had a few hours to spare so I thought I'd clear some Sphinx build
> warnings/errors. There isn't anything too controversial here. The only
> interesting thing I hit was in patch 7 (docs: Remove unknown 'hint'
> directive), I couldn't work out if this was a serious directive, a joke,
> or a typo.
Hi Tobin,
the problem was a missing empty line (see my comment on this patch).
The reST primer from sphinx-doc is always a good reference for the daily work
http://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html#directives
-- Markus --
next prev parent reply other threads:[~2019-03-08 8:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-07 21:11 [PATCH 0/9] docs: Fix various build warnings/errors Tobin C. Harding
2019-03-07 21:11 ` [PATCH 1/9] docs: Fix spelling mistake Tobin C. Harding
2019-03-07 21:11 ` [PATCH 2/9] docs: Add colon clearing sphinx warning Tobin C. Harding
2019-03-07 21:11 ` [PATCH 3/9] docs: Remove unnecessary reference link title Tobin C. Harding
2019-03-07 21:11 ` [PATCH 4/9] docs: Use reference to link to rst file Tobin C. Harding
2019-03-07 21:11 ` [PATCH 5/9] docs: Replace backtick with apostrophe Tobin C. Harding
2019-03-08 3:35 ` Randy Dunlap
2019-03-07 21:11 ` [PATCH 6/9] docs: Use correct list markup character Tobin C. Harding
2019-03-08 3:40 ` Randy Dunlap
2019-03-08 4:58 ` Tobin C. Harding
2019-03-07 21:11 ` [PATCH 7/9] docs: Remove unknown 'hint' directive Tobin C. Harding
2019-03-08 3:51 ` Randy Dunlap
2019-03-08 8:27 ` Markus Heiser
2019-03-08 16:04 ` Randy Dunlap
2019-03-08 16:35 ` Randy Dunlap
2019-03-07 21:11 ` [PATCH 8/9] docs: Fix Title underline too short warning Tobin C. Harding
2019-03-08 3:42 ` Randy Dunlap
2019-03-08 4:57 ` Tobin C. Harding
2019-03-07 21:11 ` [PATCH 9/9] docs: Add blank line after SPDX licence identifier Tobin C. Harding
2019-03-08 3:43 ` Randy Dunlap
2019-03-08 8:40 ` Markus Heiser [this message]
2019-03-08 20:16 ` [PATCH 0/9] docs: Fix various build warnings/errors Tobin C. Harding
2019-03-09 9:20 ` Markus Heiser
2019-03-25 16:33 ` Jonathan Corbet
2019-03-25 21:59 ` Tobin C. Harding
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=2b5f55e5-79d6-2538-5054-b34e4b93e721@darmarit.de \
--to=markus.heiser@darmarit.de \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tobin@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.