linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Utkin <andrey.utkin@pb.com>
To: <linux-kernel@vger.kernel.org>, <git@vger.kernel.org>
Subject: Don't use PGP/GPG signatures in mail that contains patches
Date: Mon, 18 Jan 2016 03:27:15 +0200	[thread overview]
Message-ID: <569C3F73.3090805@pb.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 38 bytes --]


________________________________


[-- Attachment #2: Type: message/rfc822, Size: 4472 bytes --]

[-- Attachment #2.1.1: Type: text/plain, Size: 645 bytes --]

===== QUOTE =====
Don't use PGP/GPG signatures in mail that contains patches.
This breaks many scripts that read and apply the patches.
(This should be fixable.)
===== END QUOTE =====

This is in Linux' Documentation/email-clients.txt since 2007, and still
almost nobody signs patch submissions. There are few brave people who
do, though, and seems it's not the end of world for any "scripts".
The broken scripts could be an excuse in 2007, but not today.

Proposal:
1. Implement signing option in git-send-email.
2. Figure out if anything fails to interoperate.
3. Drop the quoted statement or change it to appreciate signing.


[-- Attachment #2.1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2016-01-18  1:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-18  1:27 Andrey Utkin [this message]
2016-01-18 21:48 ` Don't use PGP/GPG signatures in mail that contains patches Jeff King
2016-01-19 11:52   ` Andrey Utkin
2016-01-19 21:05     ` Eric Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=569C3F73.3090805@pb.com \
    --to=andrey.utkin@pb.com \
    --cc=git@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).