public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Randy Dunlap <rdunlap@infradead.org>,
	Keith Christian <keith1christian@gmail.com>,
	Anil Nair <anilcoll90@gmail.com>,
	lkml <linux-kernel@vger.kernel.org>,
	"linux-doc\@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: Missing File REPORTING-BUGS In Linux Kernel.
Date: Mon, 08 May 2017 18:51:33 +0300	[thread overview]
Message-ID: <877f1r9wje.fsf@intel.com> (raw)
In-Reply-To: <4d08cbe8-263b-0e06-568d-9a79ef1d6ae2@infradead.org>

On Mon, 08 May 2017, Randy Dunlap <rdunlap@infradead.org> wrote:
> On 05/08/17 05:30, Keith Christian wrote:
>> Is there a link to the discussion for changing to .rst?
>
> I don't recall much discussion.  There may have been some on the
> linux-doc mailing list.

There was "some discussion" that dragged on for the better part of a
year. It spanned more threads than I care to remember. Indeed I wish I
could forget. Perhaps you already did. ;)

These articles provide some background:

https://lwn.net/Articles/671496/
https://lwn.net/Articles/692704/
https://lwn.net/Articles/692705/

> As with many things that are kernel-related, it depends a lot on who
> is doing the work and their choices and decisions.

I seem to recall there were a lot of opinions from people who couldn't
care less about documentation too. ;)

>> There is a convention for keeping essential documentation in a simple
>> format that can be read without additional processing.  Where are we
>> going with this?
>
> .rst files are still readable with an editor or 'more' etc.

Moreover, we're converting all of the DocBook XML documentation over to
rst too, making much more documentation human readable (and writable)
without additional processing.

BR,
Jani.


-- 
Jani Nikula, Intel Open Source Technology Center

  reply	other threads:[~2017-05-08 15:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-08  2:17 Missing File REPORTING-BUGS In Linux Kernel Anil Nair
2017-05-08  2:52 ` Randy Dunlap
2017-05-08 13:31   ` Keith Christian
     [not found]   ` <CAFWoy7H32z_0t=k3tSLKUZrcfkco06j9jacv130DLT=647gYpg@mail.gmail.com>
2017-05-08 15:23     ` Randy Dunlap
2017-05-08 15:51       ` Jani Nikula [this message]
2017-05-08 21:55         ` Keith Christian
     [not found]         ` <20170508215550.D35A0AE034@b01ledav005.gho.pok.ibm.com>
2017-05-09  0:31           ` Andrew Donnellan

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=877f1r9wje.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=anilcoll90@gmail.com \
    --cc=keith1christian@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox