diff options
| author | Alejandro Colomar <alx@kernel.org> | 2023-11-22 22:50:34 +0100 |
|---|---|---|
| committer | Alejandro Colomar <alx@kernel.org> | 2023-11-24 12:22:57 +0100 |
| commit | a457755cb71c94464e70a85278ff307bfb0de8ec (patch) | |
| tree | f1fdc3edbf20bf67c3599d8d8e1e2ecb6ec7cc69 | |
| parent | 2facf79eefb06e61f7563cdee5f07343cb593dd1 (diff) | |
CONTRIBUTING: Say it's us who recommend signing emails
Also link to <gnupg.org>, since they also recommend it.
Suggested-by: "G. Branden Robinson" <branden@debian.org>
Acked-by: "G. Branden Robinson" <branden@debian.org>
Signed-off-by: Alejandro Colomar <alx@kernel.org>
| -rw-r--r-- | CONTRIBUTING | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/CONTRIBUTING b/CONTRIBUTING index 7b85e7375..bde085a63 100644 --- a/CONTRIBUTING +++ b/CONTRIBUTING @@ -57,13 +57,14 @@ Description help Sign your emails with PGP - It is strongly encouraged that you sign all of your emails sent - to the mailing list, (especially) including the ones containing + We strongly encourage that you sign all of your emails sent to + the mailing list, (especially) including the ones containing patches, with your PGP key. This helps establish trust between you and other contributors of this project, and prevent others impersonating you. If you don't have a key, it's not mandatory to sign your email, but you're encouraged to create and start - using a PGP key. + using a PGP key. See also: + <https://www.gnupg.org/faq/gnupg-faq.html#use_pgpmime> There are many ways you can sign your patches, and it depends on your preferred tools. You can use git-send-email(1) in |