Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp3281559yba; Mon, 8 Apr 2019 15:19:19 -0700 (PDT) X-Google-Smtp-Source: APXvYqz8tV/1fNos4BA31pnWQkgZEz3msVlk0xqSRVOzaVLk0RVg+pVwJuEEhwmE1rvwTAxqZmoV X-Received: by 2002:a63:d5f:: with SMTP id 31mr29731273pgn.208.1554761959209; Mon, 08 Apr 2019 15:19:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1554761959; cv=none; d=google.com; s=arc-20160816; b=w1d8OvyOn1Guuw3OemIosKR9rRBJobEpEc4Ms+Y8Ynt4dPLzYDktRWkuOKoJgKH058 ySIXm6lS/PSGgBTXGTO3JbXcuAjUgxFP2iZ5D/sJ+wCz7MPZf8j9cp5IcemNolmaU63g SY9kn3AeHCyMFN835f/KvRdylO4cg0pYnCpZu9HK3CVwRM9rf3ItEAfwlb7l7xTLm99I +MZk3F/b3ciGwfoyCWAc08i4QVUxI7rAHMZog7mr0rbMcsCRD6lzknickgOm1o2YdZc8 788q/0qmrAub7CT2NV6GPtasBYp01m9yRIutXxxX+DzElYAkVo4nMKqKmHjHgljRZbLx YPTg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date; bh=2TKWO9buu2Wmwl/ETRTdNbGpihv4Nyj6PT6X3bxd5Dg=; b=sGOLqkLR6Um0rSg2xdd+iI3U5vCHS+hQvjW/4VXG/KfRBKIHxOM2F4/unnFGfnoAm1 yjoZxNhbq6k0TgUVLLI5b5mo/60JRPvEEMaPsVE3RuKoVSL9ec2BPALpRgQyeBHuevXa BWGkIFKbfnN9I26O8slkzPbwvtkSLdhebKGaL4il4txMpYvZkWaR0/9aQpiTLfvdraBq GYqRMrQr6U7sU7wcnVEg5M7LzbkPcdjBq0yUykxWIADo/qjVh5FrvRspdm8p0935bT4n Bm5DNC4NjG7Gw7DNVUSTfAr6glXvVRItF2EcQ1M4HzstjXBO8Gupa4ndr9qzXluBH8Gl a8BA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t14si10168178pfh.87.2019.04.08.15.19.03; Mon, 08 Apr 2019 15:19:19 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726938AbfDHWSW (ORCPT + 99 others); Mon, 8 Apr 2019 18:18:22 -0400 Received: from ms.lwn.net ([45.79.88.28]:38342 "EHLO ms.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726188AbfDHWSW (ORCPT ); Mon, 8 Apr 2019 18:18:22 -0400 Received: from lwn.net (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ms.lwn.net (Postfix) with ESMTPSA id 64ADF2CC; Mon, 8 Apr 2019 22:18:21 +0000 (UTC) Date: Mon, 8 Apr 2019 16:18:20 -0600 From: Jonathan Corbet To: Mauro Carvalho Chehab Cc: Linux Doc Mailing List , Mauro Carvalho Chehab , linux-kernel@vger.kernel.org Subject: Re: [PATCH 00/10] Add all documentation files to an html/pdf produced book Message-ID: <20190408161820.6a12657f@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 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 8 Apr 2019 13:58:16 -0300 Mauro Carvalho Chehab wrote: > Despite having converted almost all files to ReST at the main Documentation/ > directory, they're still not included to any book. Also, after all those years > after migrated to ReST as the official documentation format, there are still > a lot of files using plain TXT files, with random internal formatting. > > As it will likely require a lot more years to get everything converted, > let's add index.rst files to Documentation/* subdirs, with a text_files.rst > including all plain txt files as literal includes. > > That ensures that the html output will contain the entire Linux Kernel > documentation. Hmm... > 251 files changed, 5262 insertions(+), 47 deletions(-) Somebody clearly thinks I haven't been involved in enough merge conflicts recently :) I understand the goal, but I have to wonder. This feels a lot like giving up on the problem and just sweeping the remaining junk into a pile somewhere. I feel like it would, if anything, reduce the incentive to deal with these leftover documents properly. If this is *really* something we want to do, I would much rather proceed in smaller steps and preferably with the cooperation of the maintainers involved. Imposing all of this at once just seems like a way to make it highly dangerous for me to show my face a conferences... Thoughts? Thanks, jon