summaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
authorPaul Berry <stereotype441@gmail.com>2013-11-13 11:28:08 -0800
committerPaul Berry <stereotype441@gmail.com>2013-11-15 10:05:07 -0800
commit1556b55ccea75b85063c77eb7bec31764a3d6cbe (patch)
treefa979ba082a9d462b47f651811f34b161a2c03cd /HACKING
parent3d7122d3fac41d0a0fbb5120a7a735335cc3cd58 (diff)
Add a comment to HACKING describing the use of "*-by" in commit messages.
Suggested-by: Frank Henigman <fjhenigman@google.com> Reviewed-by: Frank Henigman <fjhenigman@google.com>
Diffstat (limited to 'HACKING')
-rw-r--r--HACKING6
1 files changed, 6 insertions, 0 deletions
diff --git a/HACKING b/HACKING
index 9eff4ef3e..738ae180f 100644
--- a/HACKING
+++ b/HACKING
@@ -159,6 +159,12 @@ a good place for general discussion about piglit development, such as
future plans for the project, and coordinating work between
developers.
+Note that Piglit patches use the terms "Reviewed-by", "Tested-by", and
+"Acked-by" in the same way as they are used for Linux kernel patches
+(see https://www.kernel.org/doc/Documentation/SubmittingPatches). You
+are also welcome to add a "Signed-off-by" line to your patch, but it
+is not required.
+
For developers who are new to piglit: when submitting a patch, it is
helpful to add a note (after the "---" line in the patch file)
indicating that you are new to the project and don't have commit