| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
We have quite a few dedicated developers now. To ensure that good |
| 5 |
taste is exercised, and that best practices are followed, patches |
| 6 |
should be signed. |
| 7 |
|
| 8 |
My proposals: |
| 9 |
Signed-off-by: Wrote (a substantial portion of) the patch |
| 10 |
Reviewed-by: Reviewed the patch thoroughly |
| 11 |
Tested-by: Tested the patch thoroughly |
| 12 |
Acked-by: Approved the concept but did not read the patch in detail |
| 13 |
(typically used by the maintainer of a specific portion, or our lead) |
| 14 |
Suggested-by: Designed the implementation |
| 15 |
Reported-by: Reported the bug/feature request |
| 16 |
|
| 17 |
These suggestions all stem from the Linux project. |
| 18 |
- -- |
| 19 |
Alexander |
| 20 |
alexander@××××××.net |
| 21 |
http://plaimi.net/~alexander |
| 22 |
-----BEGIN PGP SIGNATURE----- |
| 23 |
Version: GnuPG v2.0.22 (GNU/Linux) |
| 24 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
| 25 |
|
| 26 |
iF4EAREIAAYFAlLX3JsACgkQRtClrXBQc7VhEQD9FKmFbyf9zxl+hLylkhQN/kv6 |
| 27 |
o3DSM4xBr9fH4+1eokYA/3MbFLtDpli311d6ZqGD17kGLfz5wNj+5kPRATbiC256 |
| 28 |
=cJNe |
| 29 |
-----END PGP SIGNATURE----- |
Archives