From: Jakub Kicinski <kuba@kernel.org>
To: corbet@lwn.net
Cc: linux-doc@vger.kernel.org, workflows@vger.kernel.org,
Jakub Kicinski <kuba@kernel.org>
Subject: [PATCH docs] MAINTAINERS: treat Documentation/maintainer as process docs
Date: Wed, 12 Jul 2023 09:10:11 -0700 [thread overview]
Message-ID: <20230712161011.1339829-1-kuba@kernel.org> (raw)
A handful of people got caught out by the recent changes in git
which changed the format of Message-ID and broke our recommended
applyhook for adding lore links.
This was fixed in the docs by commit 2bb19e740e9b ("Documentation:
update git configuration for Link: tag") but it seems like few people
have noticed. Add maintainer directory to the process entry so that
workflows@ gets CCed.
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
---
TBH I wasn't aware / forgot this directory exists. I usually grep
Documentation/process. No real preference but I wanted to mention
the alternative of moving the directory under Documentation/process
instead..
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 99f18f6e8bc6..a04776f01186 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -6274,6 +6274,7 @@ DOCUMENTATION PROCESS
M: Jonathan Corbet <corbet@lwn.net>
S: Maintained
F: Documentation/process/
+F: Documentation/maintainer/
L: workflows@vger.kernel.org
DOCUMENTATION REPORTING ISSUES
--
2.41.0
next reply other threads:[~2023-07-12 16:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 16:10 Jakub Kicinski [this message]
2023-07-12 16:11 ` [PATCH docs] MAINTAINERS: treat Documentation/maintainer as process docs Jakub Kicinski
2023-07-12 16:20 ` Jonathan Corbet
2023-07-12 16:46 ` Jakub Kicinski
2023-07-12 21:32 ` Randy Dunlap
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=20230712161011.1339829-1-kuba@kernel.org \
--to=kuba@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=workflows@vger.kernel.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.