SubmittingPatches: discourage new trailers
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 <newren@gmail.com> Signed-off-by: Josh Soref <jsoref@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Josh Soref committed
Dec 28, 2023 at 04:55 UTC
ac9fff2bf1ca4174efeac57ff1ef43df8a6b9517
1 file changed
+3
-2
Documentation/SubmittingPatches
+3
-2
@@ -356,8 +356,9 @@ If you like, you can put extra tags at the end:
356
. `Tested-by:` is used to indicate that the person applied the patch
357
and found it to have the desired effect.
358
359
-You can also create your own tag or use one that's in common usage
360
-such as "Thanks-to:", "Based-on-patch-by:", or "Mentored-by:".
359
+While you can also create your own trailer if the situation warrants it, we
360
+encourage you to instead use one of the common trailers in this project
361
+highlighted above.
362
363
[[git-tools]]
364
=== Generate your patch using Git tools out of your commits.