From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on archive.lwn.net X-Spam-Level: X-Spam-Status: No, score=-1.7 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, FSL_HELO_FAKE,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by archive.lwn.net (Postfix) with ESMTP id C73EC7D04D for ; Tue, 23 Apr 2019 12:31:02 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726033AbfDWMbC (ORCPT ); Tue, 23 Apr 2019 08:31:02 -0400 Received: from mail-wr1-f68.google.com ([209.85.221.68]:36579 "EHLO mail-wr1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726204AbfDWMbC (ORCPT ); Tue, 23 Apr 2019 08:31:02 -0400 Received: by mail-wr1-f68.google.com with SMTP id b1so8652127wru.3; Tue, 23 Apr 2019 05:31:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=+9wxr5R3pk2oel1OfIQlHTOTnUvOX8cEZ1l94U4oBF8=; b=mizTPRShAF1dM0yfIHmgRTVxwNuSoOi0eKbP73V2j33rQDacaUAhCJuGXkvLMgTbhr RtU+YjH6ln1gfb+c7IA98DBdvSekblLz9zQzCvc1X0yZvcbolEn2kzHmMr3Trbd9X6Op pIAzfuBqkj6eWWdBNM/KJ+6zTJrjpSnpdSMoNTVl52bggJtjpgMzCgvlry6OYQfOvqbZ U0tIJIGzgplGfdFs2rwUekxic6kaFUOGcmsGindeMnkmLk1v5p1sVbEdq496JeqBwoNP 2GcEs2hJWFEtbNImdzQIjV7LE77X2sFwnxSQ4MDEYz7L/ipzVCjFKp0NbpoO+PeumJ67 zCkw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=+9wxr5R3pk2oel1OfIQlHTOTnUvOX8cEZ1l94U4oBF8=; b=lvJEdEfoN08wzR/bD/GdGYlhe3QK37eukn5iyiYrSk9qAc5siRitJAHzW353JuW+6l Kk8CLBCe4hD6QgyhZtdfU9wwQJSRuCsPtKwuQBcTNSN3Lcd/F1GN1jikz+m5NFgrCrWS E1zGSuD9f4vHJrR8hACK64p2LAYmqZLSjiKR/ZTH7rqrch/yKp6do8bi/c9OGXXE1eec pwlPLV5RdfyxtKhhNrOJpbGoE2lPU5XDsOBPvTGdLYum9RkFs6PRsX7JGhlj91eQEBhB 853zLfudnKRQuEfOB4mxkurzHLqpIpjkkLozVM95aYr5bqRbw1Q1kbOV6eeJwUYf1toB O4tg== X-Gm-Message-State: APjAAAWoIcwfUG45pYS89fNrdt3ZEFqxs5sq/RuofJvkEAVYJHrlK1DZ 5mtoTF6y+GWaEs+nwYYLyoY= X-Google-Smtp-Source: APXvYqznVXo22PgJ4A60yTTxCmKJ8qyXu+UGtlFM23tosnZ73o8aQYHrMIjQiYyi5NfqXepCIz4knA== X-Received: by 2002:adf:dc4b:: with SMTP id m11mr17589058wrj.66.1556022660471; Tue, 23 Apr 2019 05:31:00 -0700 (PDT) Received: from gmail.com (2E8B0CD5.catv.pool.telekom.hu. [46.139.12.213]) by smtp.gmail.com with ESMTPSA id v22sm2981298wml.32.2019.04.23.05.30.59 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 23 Apr 2019 05:30:59 -0700 (PDT) Date: Tue, 23 Apr 2019 14:30:57 +0200 From: Ingo Molnar To: Peter Zijlstra Cc: Mauro Carvalho Chehab , Linux Doc Mailing List , Mauro Carvalho Chehab , linux-kernel@vger.kernel.org, Jonathan Corbet , Ingo Molnar Subject: Re: [PATCH v2 38/79] docs: scheduler: convert docs to ReST and rename to *.rst Message-ID: <20190423123057.GA91497@gmail.com> References: <2a3b2b06459e0134a3af4fbf3e6f62e6d42c4d26.1555938376.git.mchehab+samsung@kernel.org> <20190423082937.GZ11158@hirez.programming.kicks-ass.net> <20190423103202.GA13655@gmail.com> <20190423111937.GM11158@hirez.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190423111937.GM11158@hirez.programming.kicks-ass.net> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-doc-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-doc@vger.kernel.org * Peter Zijlstra wrote: > On Tue, Apr 23, 2019 at 12:32:02PM +0200, Ingo Molnar wrote: > > > The .rst files still read like text files, right? > > Like a harder to read text file for no gains. I just looked through a couple of RST files in Documentation/, and they look like perfectly readable text files to me. Some of the formatting details are arguably 'special' and can be broken via "text edits" without being aware of the RST markup relevance - but I don't think it's a problem for RST-unaware developers to break that markup, the Documentation/ folks have been rather generous and flexible in fixing those up, in addition to fixing all the typos as well. So I'd be cautiously in favor of the RST conversion, assuming I don't get yelled at if I break the markup. ;-) Thanks, Ingo