From: "Tobin C. Harding" <me@tobin.cc>
To: Markus Heiser <markus.heiser@darmarit.de>
Cc: Jonathan Corbet <corbet@lwn.net>,
Mike Rapoport <rppt@linux.ibm.com>,
"Tobin C. Harding" <tobin@kernel.org>,
Christopher Lameter <cl@linux.com>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 3/3] docs: Use underscore not hyphen in label
Date: Thu, 7 Feb 2019 07:28:29 +1100 [thread overview]
Message-ID: <20190206202829.GC24938@eros.localdomain> (raw)
In-Reply-To: <c4ee1d24-6a14-d87f-3a0c-88b13e56590f@darmarit.de>
On Wed, Feb 06, 2019 at 08:49:38AM +0100, Markus Heiser wrote:
> Am 06.02.19 um 05:27 schrieb Tobin C. Harding:
> > Seems we either change them all or none of them.
>
> Both are OK .. from the spec ...
>
> "Simple reference names are single words consisting of alphanumerics plus
> isolated (no two adjacent) internal hyphens, underscores, periods, colons
> and plus signs; no whitespace or other characters are allowed." [1]
>
>
> >> Many errors are not reported again in rebuilds.
> >
> > It's more than that. Seems that no .o files means dependencies are not
> > the same in docs directories to *usual* source code directories, as in
> > this example, a file with an outdated label was not rebuilt since it
> > wasn't touched.
>
> Right, this is what they call the 'doctree' files (see [2] for build
> phases), one for every source file. ATM they are located in the hidden
> folder 'output/.doctree'. OT here, just to mentioning: this will result in
> the folder being exported at the end, e.g. kernel.org:
>
> https://www.kernel.org/doc/html/latest/.doctrees/
>
> > Note to self, always do clean build for docs patches. Thanks.
> >
> >> To reproduce this error run 'make cleandocs htmldocs' first. Then you will see
> >> this error message (I'am on current docs-next from Jon using Sphinx v1.8.3 ):
> >>
> >> Documentation/core-api/mm-api.rst:22: WARNING: undefined label: \
> >> memory-allocation (if the link has no caption ...)
> >
> > Can confirm I also get this warning,
> ..
> > With patch reverted, on docs-next, I've got 0 'undefined labels'
> > warnings.
>
> Thanks for verification.
>
> [1] http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#reference-names
> [2] http://www.sphinx-doc.org/en/master/extdev/index.html#build-phases
>
>
> -- Markus --
>
Thanks Markus, I appreciate the information.
Tobin.
prev parent reply other threads:[~2019-02-06 20:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 4:06 [PATCH 0/3] docs: vm: Fix typo and build warnings Tobin C. Harding
2019-01-31 4:06 ` [PATCH 1/3] docs: Fix SLUB docs typo Tobin C. Harding
2019-01-31 9:30 ` Mike Rapoport
2019-01-31 4:06 ` [PATCH 2/3] docs: Add missing colon Tobin C. Harding
2019-01-31 9:30 ` Mike Rapoport
2019-01-31 4:06 ` [PATCH 3/3] docs: Use underscore not hyphen in label Tobin C. Harding
2019-01-31 9:27 ` Mike Rapoport
2019-01-31 20:56 ` Tobin C. Harding
2019-02-01 23:03 ` Jonathan Corbet
2019-02-02 14:32 ` Mike Rapoport
2019-02-03 23:20 ` Tobin C. Harding
2019-02-04 8:38 ` Mike Rapoport
2019-02-04 21:12 ` Tobin C. Harding
2019-02-04 23:03 ` Jonathan Corbet
2019-02-05 8:30 ` Markus Heiser
2019-02-06 4:27 ` Tobin C. Harding
2019-02-06 7:49 ` Markus Heiser
2019-02-06 20:28 ` Tobin C. Harding [this message]
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=20190206202829.GC24938@eros.localdomain \
--to=me@tobin.cc \
--cc=cl@linux.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=markus.heiser@darmarit.de \
--cc=rppt@linux.ibm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox