From: Thorsten Leemhuis <linux@leemhuis.info>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Randy Dunlap <rdunlap@infradead.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v1 2/4] MAINTAINERS: add entry for Documentation/admin-guide/reporting-issues.rst
Date: Tue, 30 Mar 2021 16:13:05 +0200 [thread overview]
Message-ID: <c8d55ec74d104b90fdb9c155bca3b407e8480fb3.1617113469.git.linux@leemhuis.info> (raw)
In-Reply-To: <cover.1617113469.git.linux@leemhuis.info>
Thorsten will keep an eye on the new document about reporting issues
(aka bugs).
Signed-off-by: Thorsten Leemhuis <linux@leemhuis.info>
---
MAINTAINERS | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index e66ff3daf23c..b5d38fedff6c 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -5413,6 +5413,12 @@ X: Documentation/power/
X: Documentation/spi/
X: Documentation/userspace-api/media/
+DOCUMENTATION REPORTING ISSUES
+M: Thorsten Leemhuis <linux@leemhuis.info>
+L: linux-doc@vger.kernel.org
+S: Maintained
+F: Documentation/admin-guide/reporting-issues.rst
+
DOCUMENTATION SCRIPTS
M: Mauro Carvalho Chehab <mchehab@kernel.org>
L: linux-doc@vger.kernel.org
--
2.30.2
next prev parent reply other threads:[~2021-03-30 14:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 14:13 [PATCH v1 0/4] Improve reporting-issues.rst and make it official Thorsten Leemhuis
2021-03-30 14:13 ` [PATCH v1 1/4] docs: make reporting-issues.rst official and delete reporting-bugs.rst Thorsten Leemhuis
2021-03-30 14:51 ` Greg KH
2021-03-31 19:47 ` Jonathan Corbet
2021-04-05 7:43 ` Thorsten Leemhuis
2021-03-30 14:51 ` Greg KH
2021-03-31 8:33 ` Wu X.C.
2021-04-01 4:59 ` Alex Shi
2021-03-30 14:13 ` Thorsten Leemhuis [this message]
2021-03-30 14:13 ` [PATCH v1 3/4] docs: reporting-issues.rst: reshuffle and improve TLDR Thorsten Leemhuis
2021-03-30 15:17 ` Thorsten Leemhuis
2021-03-30 14:13 ` [PATCH v1 4/4] docs: reporting-issues: reduce quoting and assorted fixes Thorsten Leemhuis
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=c8d55ec74d104b90fdb9c155bca3b407e8480fb3.1617113469.git.linux@leemhuis.info \
--to=linux@leemhuis.info \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.