Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752452AbcKRJPR (ORCPT ); Fri, 18 Nov 2016 04:15:17 -0500 Received: from mga09.intel.com ([134.134.136.24]:41003 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751139AbcKRJPO (ORCPT ); Fri, 18 Nov 2016 04:15:14 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.31,656,1473145200"; d="scan'208";a="787928273" From: Jani Nikula To: Linus Torvalds , Arnd Bergmann Cc: ksummit-discuss@lists.linuxfoundation.org, "open list\:DOCUMENTATION" , Linux Kernel Mailing List , Linux Media Mailing List Subject: Re: [Ksummit-discuss] Including images on Sphinx documents In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo References: <20161107075524.49d83697@vento.lan> <11020459.EheIgy38UF@wuerfel> <20161116182633.74559ffd@vento.lan> <2923918.nyphv1Ma7d@wuerfel> Date: Fri, 18 Nov 2016 11:15:09 +0200 Message-ID: <87y40hxi76.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1310 Lines: 28 On Thu, 17 Nov 2016, Linus Torvalds wrote: > We have makefiles, but more importantly, few enough people actually > *generate* the documentation, that I think if it's an option to just > fix sphinx, we should do that instead. If it means that you have to > have some development version of sphinx, so be it. Most people read > the documentation either directly in the unprocessed text-files > ("source code") or on the web (by searching for pre-formatted docs) > that I really don't think we need to worry too much about the > toolchain. My secret plan was to make building documentation easy, and then trick more people into actually doing that on a regular basis, to ensure we keep the build working and the output sensible in a variety of environments. Sure we have a bunch of people doing this, and we have 0day doing this, but I'd hate it if it became laborous and fiddly to set up the toolchain to generate documentation. So I'm not necessarily disagreeing with anything you say, but I think there's value in having a low bar for entry (from the toolchain POV) for people interested in working with documentation, whether they're seasoned kernel developers or newcomers purely interested in documentation. BR, Jani. -- Jani Nikula, Intel Open Source Technology Center