workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <linux@leemhuis.info>
To: Jonathan Corbet <corbet@lwn.net>
Cc: workflows@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH v2 1/2] docs: 5.Posting: mentioned Suggested-by: tag
Date: Sat, 16 Nov 2024 10:33:58 +0100	[thread overview]
Message-ID: <1609d461030094b294f08d0b4e208d32993ac799.1731749544.git.linux@leemhuis.info> (raw)
In-Reply-To: <cover.1731749544.git.linux@leemhuis.info>

Mentioned the Suggested-by: tag in 5.Posting.rst in a way similar to
submitting-patches.rst, which according to the header of the latter is
the less detailed document of the two.

Signed-off-by: Thorsten Leemhuis <linux@leemhuis.info>
---
 Documentation/process/5.Posting.rst | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/Documentation/process/5.Posting.rst b/Documentation/process/5.Posting.rst
index b3eff03ea2491c..dbb763a8de901d 100644
--- a/Documentation/process/5.Posting.rst
+++ b/Documentation/process/5.Posting.rst
@@ -261,6 +261,10 @@ The tags in common use are:
    can be used instead of Closes: if the patch fixes a part of the issue(s)
    being reported.
 
+ - A Suggested-by: tag indicates that the patch idea is suggested by the person
+   named and ensures credit to the person for the idea. This will, hopefully,
+   inspire them to help us again in the future.
+
  - Cc: the named person received a copy of the patch and had the
    opportunity to comment on it.
 
-- 
2.45.0


  reply	other threads:[~2024-11-16  9:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-16  9:33 [PATCH v2 0/2] docs: reminder to not expose potentially private email addresses Thorsten Leemhuis
2024-11-16  9:33 ` Thorsten Leemhuis [this message]
2024-11-16 10:39   ` [PATCH v2 1/2] docs: 5.Posting: mentioned Suggested-by: tag Greg KH
2024-11-16  9:33 ` [PATCH v2 2/2] docs: clarify rules wrt tagging other people Thorsten Leemhuis
2024-11-16 10:42   ` Greg KH
2024-11-16 11:07     ` Thorsten Leemhuis
2024-11-16 11:50     ` Mauro Carvalho Chehab
2024-11-16 12:27       ` Thorsten Leemhuis
2024-11-16 13:16         ` Mauro Carvalho Chehab
2024-11-16 11:38   ` Geert Uytterhoeven
2024-11-16 11:51     ` 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=1609d461030094b294f08d0b4e208d32993ac799.1731749544.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox