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-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160923091501.38cc6a0b@lwn.net>
Date:   Fri, 23 Sep 2016 09:15:01 -0600
From:   Jonathan Corbet <corbet@....net>
To:     Mauro Carvalho Chehab <mchehab@...pensource.com>
Cc:     Linux Doc Mailing List <linux-doc@...r.kernel.org>,
        Mauro Carvalho Chehab <mchehab@...radead.org>,
        Mauro Carvalho Chehab <mchehab@...nel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH v3] docs-rst: user: add MAINTAINERS

On Fri, 23 Sep 2016 12:07:33 -0300
Mauro Carvalho Chehab <mchehab@...pensource.com> wrote:

> including MAINTAINERS using ReST is tricky, because all
> maintainer's entries are like:

So I'm generally in favor of moving things over to RST, but I have to ask:
what's the payoff for doing that with the MAINTAINERS file?  I *suppose*
it's documentation, but it's also really a flat-file database of
who-to-email information.  I'm not sure I see the value of including it in
the docs?  What am I missing here?

Thanks,

jon

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ