From: Jonathan Corbet <corbet@lwn.net>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scripts/documentation-file-ref-check: detect broken :doc:`foo`
Date: Fri, 3 May 2019 06:41:05 -0600 [thread overview]
Message-ID: <20190503064105.763ab1e9@lwn.net> (raw)
In-Reply-To: <a24b46d49121c4f3d90f55acc20c8efb6b0a9280.1556123129.git.mchehab+samsung@kernel.org>
On Wed, 24 Apr 2019 13:25:33 -0300
Mauro Carvalho Chehab <mchehab+samsung@kernel.org> wrote:
> As we keep migrating documents to ReST, we're starting to see
> more of such tags.
>
> Right now, all such tags are pointing to a documentation file,
> but regressions may be introduced.
>
> So, add a check for such kind of issues as well.
Applied, thanks.
jon
prev parent reply other threads:[~2019-05-03 12:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 16:25 Mauro Carvalho Chehab
2019-05-03 12:41 ` 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=20190503064105.763ab1e9@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®