[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20201110155153.29862-1-yashsri421@gmail.com>
Date: Tue, 10 Nov 2020 21:21:53 +0530
From: Aditya Srivastava <yashsri421@...il.com>
To: mchehab+huawei@...nel.org
Cc: yashsri421@...il.com, lukas.bulwahn@...il.com, joe@...ches.com,
krzk@...nel.org, gregkh@...uxfoundation.org,
grandmaster@...klimov.de, trix@...hat.com,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-kernel-mentees@...ts.linuxfoundation.org
Subject: [PATCH] checkpatch: Documentation: include sign off for reverts
Currently, we do not have any documentation on commit reverts regarding
the requirement of Signed-off-by tag for it. This may be misleading to
the users.
Evaluating MISSING_SIGN_OFF checkpatch warnings on v4.13..v5.8 showed
that 4 out of 11 cases missing a sign-off are revert commits.
Add documentation regarding the same to document the community
consensus and let readers know.
Signed-off-by: Aditya Srivastava <yashsri421@...il.com>
---
Documentation/process/submitting-patches.rst | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst
index 83d9a82055a7..ff065e1f6a25 100644
--- a/Documentation/process/submitting-patches.rst
+++ b/Documentation/process/submitting-patches.rst
@@ -404,6 +404,8 @@ then you just add a line saying::
using your real name (sorry, no pseudonyms or anonymous contributions.)
This will be done for you automatically if you use ``git commit -s``.
+Also reverts should include a Signed-off-by. ``git revert -s`` does
+that for you.
Some people also put extra tags at the end. They'll just be ignored for
now, but you can do this to mark internal company procedures or just
--
2.17.1
Powered by blists - more mailing lists