All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Silvio Fricke <silvio.fricke@gmail.com>,
	linux-doc@vger.kernel.org, Ming Lei <ming.lei@canonical.com>,
	"Luis R . Rodriguez" <mcgrof@kernel.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/4] Documentation/atomic_ops.txt: convert to ReST markup
Date: Mon, 28 Nov 2016 12:56:41 +0100	[thread overview]
Message-ID: <20161128115641.GX3092@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <87fumb26si.fsf@intel.com>

On Mon, Nov 28, 2016 at 01:16:45PM +0200, Jani Nikula wrote:
> Using rst we can produce decent HTML pages, and make them available at
> [1], in context. You don't have to read that, but it will be a lot more
> discoverable for other people, another important quality of good
> documentation. And perhaps you don't have to tell people to go read it
> so much.
> 
> [1] https://www.kernel.org/doc/html/latest/

*sigh*, basically if I have to touch a browser its broken.

> > Very much agreed, once a file is no longer readable with less or the
> > text editor of your choice, it as good doesn't exist at all. So I very
> > much worry about RST even supporting such heavy markup that the end
> > result is unreadable.
> 
> The goal is to have the best of both worlds, keeping it pretty much
> plain text, but adding just enough consistency in formatting that you
> can generate other formats out of it. We don't have to and we shouldn't
> go overboard with the markup.
> 
> Arguably you could call rst a "coding style" for plain text. We have
> pretty uniform C code, I don't think it's unreasonable to have a little
> bit of consistency in the plain text. And really, it's not much we're
> asking.

With some decidedly daft conventions though; see my email to Mauro.

  reply	other threads:[~2016-11-28 11:56 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-24 12:42 [PATCH 0/4] core-api ReST: assoc_array, atomic_ops, local_ops Silvio Fricke
2016-11-24 12:42 ` [PATCH 1/4] Documentation/assoc_array.txt: convert to ReST markup Silvio Fricke
2016-11-24 12:42 ` [PATCH 2/4] Documentation/atomic_ops.txt: " Silvio Fricke
2016-11-24 12:42 ` [PATCH 3/4] Documentation/local_ops.txt: " Silvio Fricke
2016-11-24 12:42 ` [PATCH 4/4] firmware: remove warning at documentation generation time Silvio Fricke
2016-11-24 19:46 ` [PATCH 0/4] core-api ReST: assoc_array, atomic_ops, local_ops Mauro Carvalho Chehab
2016-11-25 10:02 ` [PATCH v2 " Silvio Fricke
2016-11-25 10:02   ` [PATCH v2 1/4] Documentation/assoc_array.txt: convert to ReST markup Silvio Fricke
2016-11-25 13:03     ` Mauro Carvalho Chehab
2016-11-25 10:02   ` [PATCH v2 2/4] Documentation/atomic_ops.txt: " Silvio Fricke
2016-11-25 13:25     ` Mauro Carvalho Chehab
2016-11-25 10:02   ` [PATCH v2 3/4] Documentation/local_ops.txt: " Silvio Fricke
2016-11-25 13:34     ` Mauro Carvalho Chehab
2016-11-25 13:47       ` S. Fricke
2016-11-25 13:58         ` Mauro Carvalho Chehab
2016-11-25 10:02   ` [PATCH v2 4/4] firmware: remove warning at documentation generation time Silvio Fricke
2016-11-25 13:34     ` Mauro Carvalho Chehab
2016-11-25 14:59   ` [PATCH v3 0/4] core-api ReST: assoc_array, atomic_ops, local_ops Silvio Fricke
2016-11-25 14:59     ` [PATCH v3 1/4] Documentation/assoc_array.txt: convert to ReST markup Silvio Fricke
2016-11-25 20:53       ` Mauro Carvalho Chehab
2016-11-25 14:59     ` [PATCH v3 2/4] Documentation/atomic_ops.txt: " Silvio Fricke
2016-11-25 21:01       ` Mauro Carvalho Chehab
2016-11-25 21:58       ` Peter Zijlstra
2016-11-27 14:53         ` S. Fricke
2016-11-27 18:36           ` Jani Nikula
2016-11-27 23:59         ` Jonathan Corbet
2016-11-28  7:26           ` Peter Zijlstra
2016-11-28  8:44             ` Daniel Vetter
2016-11-28 10:20               ` Peter Zijlstra
2016-11-28 11:08                 ` Mauro Carvalho Chehab
2016-11-28 11:54                   ` Peter Zijlstra
2016-11-28 13:46                     ` Daniel Vetter
2016-11-28 15:14                       ` Mauro Carvalho Chehab
2016-11-28 11:16                 ` Jani Nikula
2016-11-28 11:56                   ` Peter Zijlstra [this message]
2016-11-28 12:32                     ` Jani Nikula
2016-11-28 14:13                 ` Daniel Vetter
2016-11-28 14:29                   ` Jonathan Corbet
2016-11-25 14:59     ` [PATCH v3 3/4] Documentation/local_ops.txt: " Silvio Fricke
2016-11-25 21:10       ` Mauro Carvalho Chehab
2016-11-25 14:59     ` [PATCH v3 4/4] firmware: remove warning at documentation generation time Silvio Fricke
2016-11-25 20:50       ` Mauro Carvalho Chehab
2016-12-01 16:11         ` Luis R. Rodriguez
2016-12-01 16:45           ` Greg Kroah-Hartman
2016-11-28 17:30     ` [PATCH v4 0/4] core-api ReST: assoc_array, atomic_ops, local_ops Silvio Fricke
2016-11-28 17:30       ` [PATCH v4 1/4] Documentation/assoc_array.txt: convert to ReST markup Silvio Fricke
2016-11-28 17:30       ` [PATCH v4 2/4] Documentation/local_ops.txt: " Silvio Fricke
2016-11-28 17:30       ` [PATCH v4 3/4] Documentation/atomic_ops.txt: " Silvio Fricke
2016-11-28 17:30       ` [PATCH v4 4/4] firmware: remove warning at documentation generation time Silvio Fricke
2016-12-01  0:51       ` [PATCH v4 0/4] core-api ReST: assoc_array, atomic_ops, local_ops Jonathan Corbet
2016-12-01 15:49         ` Luis R. Rodriguez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161128115641.GX3092@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=corbet@lwn.net \
    --cc=jani.nikula@linux.intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=mchehab@kernel.org \
    --cc=ming.lei@canonical.com \
    --cc=silvio.fricke@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.