diff options
author | Paul Berry <stereotype441@gmail.com> | 2013-11-13 11:28:08 -0800 |
---|---|---|
committer | Paul Berry <stereotype441@gmail.com> | 2013-11-15 10:05:07 -0800 |
commit | 1556b55ccea75b85063c77eb7bec31764a3d6cbe (patch) | |
tree | fa979ba082a9d462b47f651811f34b161a2c03cd | |
parent | 3d7122d3fac41d0a0fbb5120a7a735335cc3cd58 (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>
-rw-r--r-- | HACKING | 6 |
1 files changed, 6 insertions, 0 deletions
@@ -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 |