From: Borislav Petkov <bp@alien8.de>
To: Jonathan Corbet <corbet@lwn.net>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: [PATCH] Documentation/submitting-patches: Document RESEND tag on patches
Date: Tue, 13 Apr 2021 13:38:34 +0200 [thread overview]
Message-ID: <20210413113834.GE16519@zn.tnic> (raw)
In-Reply-To: <20201217183756.GE23634@zn.tnic>
Hi Jon,
here's the next piece of documentation which should be generic enough.
Thx.
---
From: Borislav Petkov <bp@suse.de>
Date: Tue, 13 Apr 2021 13:26:29 +0200
Explain when a submitter should tag a patch or a patch series with the
"RESEND" tag.
This has been partially carved out from a tip subsystem handbook
patchset by Thomas Gleixner:
https://lkml.kernel.org/r/20181107171010.421878737@linutronix.de
and incorporates follow-on comments.
Signed-off-by: Borislav Petkov <bp@suse.de>
---
Documentation/process/submitting-patches.rst | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst
index ab92d9ccd39a..9284735e0b34 100644
--- a/Documentation/process/submitting-patches.rst
+++ b/Documentation/process/submitting-patches.rst
@@ -346,6 +346,16 @@ that you have sent your patches to the right place. Wait for a minimum of
one week before resubmitting or pinging reviewers - possibly longer during
busy times like merge windows.
+It's also ok to resend the patch or the patch series after a couple of
+weeks with the word "RESEND" added to the subject line::
+
+ [PATCH Vx RESEND] sub/sys: Condensed patch summary
+
+Don't add "RESEND" when you are submitting a modified version of your
+patch or patch series - "RESEND" only applies to resubmission of a
+patch or patch series which have not been modified in any way from the
+previous submission.
+
Include PATCH in the subject
-----------------------------
--
2.29.2
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2021-04-13 11:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 18:37 [PATCH] Documentation/submitting-patches: Document the SoB chain Borislav Petkov
2020-12-21 16:54 ` Jonathan Corbet
2020-12-22 13:05 ` [PATCH] Documentation/submitting-patches: Add blurb about backtraces in commit messages Borislav Petkov
2020-12-22 18:59 ` Sean Christopherson
2020-12-22 19:25 ` Borislav Petkov
2020-12-28 17:59 ` Sean Christopherson
2020-12-28 18:15 ` Borislav Petkov
2020-12-28 19:02 ` Sean Christopherson
2021-01-04 23:19 ` Jonathan Corbet
2021-01-05 10:48 ` Borislav Petkov
2021-02-02 15:43 ` Borislav Petkov
2021-02-04 21:20 ` Jonathan Corbet
2021-02-15 14:19 ` [PATCH] Documentation/submitting-patches: Extend commit message layout description Borislav Petkov
2021-02-25 11:40 ` Robert Richter
2021-03-01 22:10 ` Jonathan Corbet
2021-04-13 11:38 ` Borislav Petkov [this message]
2021-04-13 21:02 ` [PATCH] Documentation/submitting-patches: Document RESEND tag on patches Jonathan Corbet
2021-04-15 6:05 ` Borislav Petkov
2021-05-31 14:35 ` Borislav Petkov
2021-06-01 22:27 ` Jonathan Corbet
2021-06-01 22:31 ` Randy Dunlap
2021-06-01 22:37 ` Borislav Petkov
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=20210413113834.GE16519@zn.tnic \
--to=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).