From: Jonathan Corbet <corbet@lwn.net>
To: Tom Saeger <tom.saeger@oracle.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/8] Documentation: fix invalid Documentation refs (1)
Date: Thu, 12 Oct 2017 11:24:25 -0600 [thread overview]
Message-ID: <20171012112425.7f67cfca@lwn.net> (raw)
In-Reply-To: <cover.1507653969.git.tom.saeger@oracle.com>
On Tue, 10 Oct 2017 12:35:58 -0500
Tom Saeger <tom.saeger@oracle.com> wrote:
> Recently, while reading up on binfmt I attempted to open a document ref
> only to find it was invalid. I did a quick grep, found all the
> binfmt_misc related broken refs and sent a patch.
>
> Fine. Easy.
>
> Then I wondered, "how many broken doc refs are there?".
>
> Turns out with all the recent doc moves, quite a few.
>
> I went about fixing just those found in Documentation/,
> except those in Documentation/translations/ and
> Documentation/devicetree/ for now.
>
> Most of these changes were s/txt/rst/ or fixing up a path to an obvious
> new location. Some required going back to v4.10 v4.4 or some other
> version to sleuth-out what content was actually being referenced and
> then fixing the reference to point to the new file with that content.
>
> This is batch 1.
I've applied the set to the docs tree, thanks.
jon
next prev parent reply other threads:[~2017-10-12 17:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 17:35 [PATCH 0/8] Documentation: fix invalid Documentation refs (1) Tom Saeger
2017-10-10 17:36 ` [PATCH 1/8] Documentation: fix driver-api doc refs Tom Saeger
2017-10-10 21:39 ` Rafael J. Wysocki
2017-10-10 17:36 ` [PATCH 2/8] Documentation: fix admin-guide " Tom Saeger
2017-10-10 21:40 ` Rafael J. Wysocki
2017-10-10 17:36 ` [PATCH 3/8] Documentation: fix input related " Tom Saeger
2017-10-10 18:08 ` Takashi Iwai
2017-10-10 18:08 ` Takashi Iwai
2017-10-10 17:36 ` [PATCH 4/8] Documentation: fix security " Tom Saeger
2017-10-10 17:36 ` [PATCH 5/8] Documentation: fix media " Tom Saeger
2017-10-10 17:36 ` [PATCH 6/8] Documentation: fix sound " Tom Saeger
2017-10-10 18:09 ` Takashi Iwai
2017-10-10 18:09 ` Takashi Iwai
2017-10-10 17:36 ` [PATCH 7/8] Documentation: fix usb " Tom Saeger
2017-10-10 17:37 ` [PATCH 8/8] Documentation: fix networking " Tom Saeger
2017-10-12 17:24 ` Jonathan Corbet [this message]
2017-10-12 19:01 ` [PATCH 0/8] Documentation: fix invalid Documentation refs (1) Tom Saeger
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=20171012112425.7f67cfca@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tom.saeger@oracle.com \
/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.