mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: 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, 8 May 2017 08:23:32 -0700	[thread overview]
Message-ID: <4d08cbe8-263b-0e06-568d-9a79ef1d6ae2@infradead.org> (raw)
In-Reply-To: <CAFWoy7H32z_0t=k3tSLKUZrcfkco06j9jacv130DLT=647gYpg@mail.gmail.com>

On 05/08/17 05:30, Keith Christian wrote:
> 
> 
>     In v4.10, the file was moved (and renamed and edited) to
>     "Documentation/admin-guide/reporting-bugs.rst".
> 
>     I suppose that some Debian install script needs to be updated.
> 
> 
> 
> 
> Kernel hackers,
> 
> Thanks for all the work over the years on the kernel.  My very first post to the list (as a long time reader) is a question:
> 
> Were other plain text files changed to .rst as well?

[adding linux-doc mailing list]


Quite a number have been changed.

> 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.

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

> 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.

-- 
~Randy

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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-08  2:17 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 [this message]
2017-05-08 15:51       ` Jani Nikula
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=4d08cbe8-263b-0e06-568d-9a79ef1d6ae2@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=anilcoll90@gmail.com \
    --cc=keith1christian@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®