linux-kernel - Re: Missing File REPORTING-BUGS In Linux Kernel.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <4d08cbe8-263b-0e06-568d-9a79ef1d6ae2@infradead.org>
Date:   Mon, 8 May 2017 08:23:32 -0700
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Keith Christian <keith1christian@...il.com>,
        Anil Nair <anilcoll90@...il.com>,
        lkml <linux-kernel@...r.kernel.org>,
        "linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>
Subject: Re: Missing File REPORTING-BUGS In Linux Kernel.

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