linux-kernel - Re: [PATCH 0/8] Documentation: fix invalid Documentation refs (1)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20171012112425.7f67cfca@lwn.net>
Date:   Thu, 12 Oct 2017 11:24:25 -0600
From:   Jonathan Corbet <corbet@....net>
To:     Tom Saeger <tom.saeger@...cle.com>
Cc:     linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/8] Documentation: fix invalid Documentation refs (1)

On Tue, 10 Oct 2017 12:35:58 -0500
Tom Saeger <tom.saeger@...cle.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