| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <20220809133649.2235524-1-carnil@debian.org>
Date: Tue, 9 Aug 2022 15:36:49 +0200
From: Salvatore Bonaccorso <carnil@...ian.org>
To: Jonathan Corbet <corbet@....net>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Sasha Levin <sashal@...nel.org>, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org,
Salvatore Bonaccorso <carnil@...ian.org>
Subject: [PATCH v2] Documentation: stable: Document alternative for referring upstream commit hash
Additionally to the "commit <sha1> upstream." variant, "[ Upstream
commit <sha1> ]" is used as well as alternative to refer to the upstream
commit hash.
Signed-off-by: Salvatore Bonaccorso <carnil@...ian.org>
---
Changes in v2:
- Drop extra RST markup which just only clutters things without any
advantage.
Documentation/process/stable-kernel-rules.rst | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Documentation/process/stable-kernel-rules.rst b/Documentation/process/stable-kernel-rules.rst
index c61865e91f52..beef21280d88 100644
--- a/Documentation/process/stable-kernel-rules.rst
+++ b/Documentation/process/stable-kernel-rules.rst
@@ -97,6 +97,10 @@ text, like this:
commit <sha1> upstream.
+or alternatively::
+
+ [ Upstream commit <sha1> ]
+
Additionally, some patches submitted via :ref:`option_1` may have additional
patch prerequisites which can be cherry-picked. This can be specified in the
following format in the sign-off area:
--
2.36.1
Powered by blists - more mailing lists