[PATCH v3 4/9] SubmittingPatches: discourage new trailers
From: Josh Soref via GitGitGadget <hidden>
Date: 2023-12-28 04:55:32
Subsystem:
documentation, the rest · Maintainers:
Jonathan Corbet, Linus Torvalds
From: Josh Soref <redacted> There seems to be consensus amongst the core Git community on a working set of common trailers, and there are non-trivial costs to people inventing new trailers (research to discover what they mean/how they differ from existing trailers) such that inventing new ones is generally unwarranted and not something to be recommended to new contributors. Suggested-by: Elijah Newren <redacted> Signed-off-by: Josh Soref <redacted> --- Documentation/SubmittingPatches | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index 32e90238777..58dfe405049 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches@@ -356,8 +356,9 @@ If you like, you can put extra tags at the end: . `Tested-by:` is used to indicate that the person applied the patch and found it to have the desired effect. -You can also create your own tag or use one that's in common usage -such as "Thanks-to:", "Based-on-patch-by:", or "Mentored-by:". +While you can also create your own trailer if the situation warrants it, we +encourage you to instead use one of the common trailers in this project +highlighted above. [[git-tools]] === Generate your patch using Git tools out of your commits.
--
gitgitgadget