From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754774AbdJLRY3 (ORCPT ); Thu, 12 Oct 2017 13:24:29 -0400 Received: from ms.lwn.net ([45.79.88.28]:58300 "EHLO ms.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751040AbdJLRY1 (ORCPT ); Thu, 12 Oct 2017 13:24:27 -0400 Date: Thu, 12 Oct 2017 11:24:25 -0600 From: Jonathan Corbet To: Tom Saeger Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/8] Documentation: fix invalid Documentation refs (1) Message-ID: <20171012112425.7f67cfca@lwn.net> In-Reply-To: References: Organization: LWN.net MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 10 Oct 2017 12:35:58 -0500 Tom Saeger 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