From: Jonathan Corbet <corbet@lwn.net>
To: NeilBrown <neilb@suse.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
"linux-doc\@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: [PATCH] Documentation/filesystems: fix title underline lengths in path-lookup.rst
Date: Mon, 7 Jan 2019 15:25:34 -0700 [thread overview]
Message-ID: <20190107152534.07bf648c@lwn.net> (raw)
In-Reply-To: <87k1jhjeni.fsf@notabene.neil.brown.name>
On Mon, 07 Jan 2019 15:05:37 +1100
NeilBrown <neilb@suse.com> wrote:
> I probably did, but I didn't notice them.
> I just ran "make htmldocs" and there are pages and pages of warnings.
> When I look closely they do include these ones. At the time I was more
> focused on getting the output to look right.
The warning situation is really out of hand, and has been for a long
time. For a while I was trying to whack them (and Randy has done some),
but it needs a more focused effort. Someday...
Meanwhile, I've applied this one, thanks.
jon
prev parent reply other threads:[~2019-01-07 22:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 3:19 [PATCH] Documentation/filesystems: fix title underline lengths in path-lookup.rst Randy Dunlap
2019-01-07 4:05 ` NeilBrown
2019-01-07 22:25 ` Jonathan Corbet [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=20190107152534.07bf648c@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=neilb@suse.com \
--cc=rdunlap@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).