From: Andrew Morton <akpm@linux-foundation.org>
To: rdunlap@xenotime.net, joe@perches.com,
gregkh@linuxfoundation.org, corbet@lwn.net,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org
Subject: [patch 1/1] submitting-patches.rst: suggest a Link: after Reported-by:
Date: Thu, 23 Feb 2023 17:47:31 -0800 [thread overview]
Message-ID: <20230224014731.ECB6DC433EF@smtp.kernel.org> (raw)
From: Andrew Morton <akpm@linux-foundation.org>
Subject: submitting-patches.rst: suggest a Link: after Reported-by:
Date: Thu Feb 23 05:41:49 PM PST 2023
It seems to be the new way and I find it super useful.
Cc: Joe Perches <joe@perches.com>
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jonathan Corbet <corbet@lwn.net>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
--- a/Documentation/process/submitting-patches.rst~submitting-patchesrst-suggest-a-link-after-reported-by
+++ a/Documentation/process/submitting-patches.rst
@@ -501,6 +501,12 @@ the bug was reported in private, then as
Reported-by tag. The tag is intended for bugs; please do not use it to credit
feature requests.
+Where possible, please include a Link: to the report on the line
+immediately following the Reported-by:. For example,
+
+Reported-by: John Doe <john.doe@gmail.com>
+ Link: https://lkml.kernel.org/r/02f796c7@gmail.com
+
A Tested-by: tag indicates that the patch has been successfully tested (in
some environment) by the person named. This tag informs maintainers that
some testing has been performed, provides a means to locate testers for
_
next reply other threads:[~2023-02-24 1:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 1:47 Andrew Morton [this message]
2023-02-24 2:59 ` [patch 1/1] submitting-patches.rst: suggest a Link: after Reported-by: Akira Yokosawa
2023-02-24 3:01 ` Andrew Morton
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=20230224014731.ECB6DC433EF@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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