[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160923123508.59e243b9@vento.lan>
Date: Fri, 23 Sep 2016 12:35:08 -0300
From: Mauro Carvalho Chehab <mchehab@...pensource.com>
To: Jonathan Corbet <corbet@....net>
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
Em Fri, 23 Sep 2016 09:15:01 -0600
Jonathan Corbet <corbet@....net> escreveu:
> 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?
It is part of the REPORTING-BUGS procedure to check MAINTAINERS and
find to what ML the bug should be reported:
https://mchehab.fedorapeople.org/user/REPORTING-BUGS.html#how-to-report-linux-kernel-bugs
I _suspect_ that the vast majority of Linux users don't read the
MAINTAINERS file, but, instead, just google at the net for an answer
to their troubles.
By having it on an html file, together with other user's documentation,
the payoff is that more people should do the right thing when seeking for
bug resolutions at the right mailing lists or when reporting bugs,
ultimately helping to improve the Kernel quality.
Regards,
Mauro
Powered by blists - more mailing lists