all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eric Bavier <ericbavier@centurylink.net>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: New git signing key for Eric Bavier?
Date: Sun, 18 Jun 2017 13:04:52 -0500	[thread overview]
Message-ID: <20170618130452.2a36de2e@centurylink.net> (raw)
In-Reply-To: <87lgop6exs.fsf_-_@netris.org>

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

On Sun, 18 Jun 2017 01:30:07 -0400
Mark H Weaver <mhw@netris.org> wrote:

> Hi Eric,
> 
> bavier@member.fsf.org (Eric Bavier) writes:
> > bavier pushed a commit to branch master
> > in repository guix.
> >
> > commit d56c55fffbe962cf7c44030ae4eac53ffa1e1f85
> > Author: Eric Bavier <bavier@member.fsf.org>
> > Date:   Thu Jun 15 00:37:17 2017 -0500
> >
> >     gnu: tomb: Upgrade to 2.4.  
> 
> This commit, and another recent commit (e0c9530) of yours, were signed
> using a key that's different from the one you've previously used to sign
> commits, and different from the key you have registered on Savannah.
> 
> Can you please confirm that A0C5E3522EF8EF5C64CDB7F0FD73CAC719D32566 is
> your new key,

That is indeed my new key.

> sign it with your old key if possible, and upload this new
> key to Savannah?

I've just put the new key on Savannah.  It should be signed with my old
key.

Thanks for saying something.  I'm still learning things about gpg.

`~Eric

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

      reply	other threads:[~2017-06-18 18:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170615054053.5774.37195@vcs0.savannah.gnu.org>
     [not found] ` <20170615054054.70F3C20E75@vcs0.savannah.gnu.org>
2017-06-18  5:30   ` New git signing key for Eric Bavier? Mark H Weaver
2017-06-18 18:04     ` Eric Bavier [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=20170618130452.2a36de2e@centurylink.net \
    --to=ericbavier@centurylink.net \
    --cc=guix-devel@gnu.org \
    --cc=mhw@netris.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.