From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Install gpg2 as gpg
Date: Sun, 24 Jul 2016 17:10:39 -0400 [thread overview]
Message-ID: <20160724211039.GB17536@jasmine> (raw)
In-Reply-To: <87oa5mah7e.fsf@gnu.org>
On Sun, Jul 24, 2016 at 10:56:05PM +0200, Ludovic Courtès wrote:
> ludo@gnu.org (Ludovic Courtès) skribis:
>
> > Leo Famulari <leo@famulari.name> skribis:
> >
> >> On Thu, Jun 16, 2016 at 12:56:58PM +0200, Ludovic Courtès wrote:
>
> [...]
>
> >>> Anyway, this patch is just about how we name the command. That the
> >>> command is called ‘gpg2’ is a well-known annoyance, and Werner
> >>> recommends not doing that anyway.
> >>
> >> Is there a consensus on the way forward? Should we apply this patch to
> >> gnupg-2.1?
> >
> > To me it seems the answer is “yes”. If you want to be sure, please
> > leave another couple of days before pushing. :-)
> >
> >> Is anyone willing to test and maintain patches against gnupg-2.0 (not
> >> me)?
>
> I finally did that in commit bc85b127df622575988f8e760f72d608d0900a75.
>
> Now, gnupg@2.0 provides the ‘gpg’ and ‘gpgv’ commands, in addition to
> ‘gpg2’ and ‘gpgv2’ (to ease transition).
And I just pushed a change that has a similar effect for gnupg@2.1 as
163708a66.
prev parent reply other threads:[~2016-07-24 21:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 19:55 Install gpg2 as gpg Leo Famulari
2016-06-13 20:24 ` ng0
2016-06-13 21:07 ` Leo Famulari
2016-06-14 7:52 ` Andreas Enge
2016-06-14 12:07 ` Ludovic Courtès
2016-06-14 12:49 ` ng0
2016-06-14 13:37 ` Leo Famulari
2016-06-13 21:42 ` Christopher Allan Webber
2016-06-14 12:09 ` Ludovic Courtès
2016-06-14 13:50 ` Leo Famulari
2016-06-15 12:53 ` Andreas Enge
2016-06-15 15:02 ` Leo Famulari
2016-06-15 15:54 ` Andreas Enge
2016-06-16 10:56 ` Ludovic Courtès
2016-06-18 1:07 ` Leo Famulari
2016-06-19 14:03 ` Ludovic Courtès
2016-07-24 20:56 ` Ludovic Courtès
2016-07-24 21:10 ` Leo Famulari [this message]
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=20160724211039.GB17536@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.