Documentation/submitting-patches: Document the SoB chain (9bf19b78) · Commits · 戴 / test

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> Link: https://lore.kernel.org/r/20201217183756.GE23634@zn.tnic Signed-off-by:

Jonathan Corbet <corbet@lwn.net>

Documentation/process/submitting-patches.rst

+6 −0

Original line number	Diff line number	Diff line
		@@ -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:
		------------------------------------------------

Admin message