Messages in this thread Patch in this message | | | Date | Thu, 17 Dec 2020 19:37:56 +0100 | From | Borislav Petkov <> | Subject | [PATCH] Documentation/submitting-patches: Document the SoB chain |
| |
Hi Jon,
ok, let's start slow and with something that should not need a whole lot of bikeshedding. We have been repeating that a lot of times in the past which means that, especially new submitters, do not know it. So here it goes.
Btw, pls let me know when you start queueing the patches, on which tree you do that so that I can send you the following ones ontop.
Also, pls have a look here and let me know what else you want moved to generic docs:
https://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git/log/?h=rc0%2b0-tip-handbook
Otherwise I'll go by my judgement, hoping that no tip-specific stuff leaks out. :-)
Thx.
--- From: Borislav Petkov <bp@suse.de> Subject: [PATCH] Documentation/submitting-patches: Document the SoB chain
Document what a chain of Signed-off-by's in a patch commit message should mean, explicitly.
This has been 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 | 6 ++++++ 1 file changed, 6 insertions(+)
diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst index fb8261a4be30..54d761319875 100644 --- a/Documentation/process/submitting-patches.rst +++ b/Documentation/process/submitting-patches.rst @@ -411,6 +411,12 @@ 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 point out some special detail about the sign-off. +Any further SoBs (Signed-off-by:'s) following the author's SoB are from +people handling and transporting the patch, but were not involved in its +development. SoB chains should reflect the **real** route a patch took +as it was propagated to the maintainers and ultimately to Linus, with +the first SoB entry signalling primary authorship of a single author. + When to use Acked-by:, Cc:, and Co-developed-by: ------------------------------------------------ -- 2.29.2
-- Regards/Gruss, Boris.
https://people.kernel.org/tglx/notes-about-netiquette
| |