From: Christian Hesse <mail@eworm.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Michael J Gruber" <git@drmicha.warpmail.net>,
"Torsten Bögershausen" <tboegi@web.de>,
git@vger.kernel.org
Subject: Re: [PATCH 1/1] skip RFC1991 tests with gnupg 2.1.x
Date: Fri, 12 Dec 2014 09:35:43 +0100 [thread overview]
Message-ID: <20141212093543.5175e7a5@leda.localdomain> (raw)
In-Reply-To: <xmqqegs5dbqu.fsf@gitster.dls.corp.google.com>
[-- Attachment #1: Type: text/plain, Size: 860 bytes --]
Junio C Hamano <gitster@pobox.com> on Thu, 2014/12/11 15:10:
> Christian Hesse <mail@eworm.de> writes:
>
> > However... Even if GnuPG 2.2.x (or whatever future release) will become
> > next stable: It will not reintroduce support for rfc1991.
>
> How certain are we about the deprecation?
The sixth beta of GnuPG [0] had this change:
* gpg: Removed the option --pgp2 and --rfc1991 and the ability to
create PGP-2 compatible messages.
> It also would make us feel safer if we did not have to depend on the
> version or keyfile format (which would not have anything to do with
> the decision to support or not to support rfc1991 format) to check
> if the feature is supported, but that is a separate issue.
Changed in next version.
[0] http://lists.gnupg.org/pipermail/gnupg-announce/2014q3/000354.html
--
Best regards,
Chris
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-12-12 8:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 9:30 [PATCH 1/1] skip RFC1991 tests with gnupg 2.1.x Christian Hesse
2014-12-11 15:32 ` Torsten Bögershausen
2014-12-11 16:54 ` Michael J Gruber
2014-12-11 22:44 ` Christian Hesse
2014-12-11 23:10 ` Junio C Hamano
2014-12-12 8:35 ` Christian Hesse [this message]
2014-12-12 9:54 ` Christian Hesse
2014-12-12 16:00 ` Michael J Gruber
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=20141212093543.5175e7a5@leda.localdomain \
--to=mail@eworm.de \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=tboegi@web.de \
/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).