From: Markus Heiser <markus.heiser@darmarit.de>
To: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH v3] docs-rst: user: add MAINTAINERS
Date: Fri, 23 Sep 2016 18:26:50 +0200 [thread overview]
Message-ID: <DBE4DBFF-0F1B-4178-A394-11F74894985A@darmarit.de> (raw)
In-Reply-To: <20160923123508.59e243b9@vento.lan>
Am 23.09.2016 um 17:35 schrieb Mauro Carvalho Chehab <mchehab@s-opensource.com>:
> Em Fri, 23 Sep 2016 09:15:01 -0600
> Jonathan Corbet <corbet@lwn.net> escreveu:
>> 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.
>
my 2cent: and whats about a simple link into the repo?
* http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/MAINTAINERS#n123
with a hint on using scripts/get_maintainer.pl ...
-- Markus --
next prev parent reply other threads:[~2016-09-23 16:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 15:07 [RFC PATCH v3] docs-rst: user: add MAINTAINERS Mauro Carvalho Chehab
2016-09-23 15:15 ` Jonathan Corbet
2016-09-23 15:35 ` Mauro Carvalho Chehab
2016-09-23 16:26 ` Markus Heiser [this message]
2016-09-23 16:26 ` Joe Perches
2016-09-23 17:50 ` Mauro Carvalho Chehab
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=DBE4DBFF-0F1B-4178-A394-11F74894985A@darmarit.de \
--to=markus.heiser@darmarit.de \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=mchehab@kernel.org \
--cc=mchehab@s-opensource.com \
/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;
as well as URLs for NNTP newsgroup(s).