> >> Do not PGP sign your patch, at least *for now*. (...) > And maybe these 2 small words are the bug in the documentation? Shall we drop the "at least for now" part, like so: ---8<--- >From 2c4fe0e67451892186ff6257b20c53e088c9ec67 Mon Sep 17 00:00:00 2001 From: Stefan Beller <sbeller@xxxxxxxxxx> Date: Tue, 24 Jan 2017 16:19:13 -0800 Subject: [PATCH] SubmittingPatches: drop temporal reference for PGP signing Signed-off-by: Stefan Beller <sbeller@xxxxxxxxxx> --- Documentation/SubmittingPatches | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches index 08352deaae..28da4ad2d4 100644 --- a/Documentation/SubmittingPatches +++ b/Documentation/SubmittingPatches @@ -216,12 +216,12 @@ that it will be postponed. Exception: If your mailer is mangling patches then someone may ask you to re-send them using MIME, that is OK. -Do not PGP sign your patch, at least for now. Most likely, your -maintainer or other people on the list would not have your PGP -key and would not bother obtaining it anyway. Your patch is not -judged by who you are; a good patch from an unknown origin has a -far better chance of being accepted than a patch from a known, -respected origin that is done poorly or does incorrect things. +Do not PGP sign your patch. Most likely, your maintainer or other +people on the list would not have your PGP key and would not bother +obtaining it anyway. Your patch is not judged by who you are; a good +patch from an unknown origin has a far better chance of being accepted +than a patch from a known, respected origin that is done poorly or +does incorrect things. If you really really really really want to do a PGP signed patch, format it as "multipart/signed", not a text/plain message -- 2.11.0.495.g04f60290a0.dirty