From: Christopher Allan Webber <cwebber@dustycloud.org>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: New git signing key for Jan Nieuwenhuizen?
Date: Sun, 18 Jun 2017 15:50:33 -0500 [thread overview]
Message-ID: <87shix9g12.fsf@dustycloud.org> (raw)
In-Reply-To: <87r2yhdeco.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1989 bytes --]
Jan Nieuwenhuizen writes:
> Mark H Weaver writes:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
>>> commit ebfb71d45615698040818a68b7dc34996ff4c046
>>> gpg: Signature made Fri 16 Jun 2017 07:22:49 AM EDT
>>> gpg: using RSA key DB34CB51D25C9408156FCDD6A12F87978D701B99
>>> gpg: Can't check signature: No public key
>>> Author: Jan Nieuwenhuizen <janneke@gnu.org>
>>> Date: Thu Jun 15 19:22:00 2017 +0200
>>>
>>> tests: Allow setting of qemu memory-size for system tests.
>>>
>>> * gnu/system/vm.scm (common-qemu-options): Remove hardcoded "-m 256".
>>> (system-qemu-image/shared-store-script): New keyword argument: #:memory-size.
>>
>> This commit was signed using a different key than the one you've been
>> using for your other commits, and different from the one you have
>> registered on Savannah.
>>
>> Is DB34CB51D25C9408156FCDD6A12F87978D701B99 your key?
>
> Yes, that's my new key. Oops. I have updated my key on savannah.
> janneke
> -----BEGIN PGP SIGNATURE-----
>
> iQIzBAEBCAAdFiEE2zTLUdJclAgVb83WoS+Hl41wG5kFAllGFv4ACgkQoS+Hl41w
> G5mcHg/+Pd3AvBLSmoPUrXrhFcFrhQyVdq/d6f2R0JiSkrPy402P003Bp6pzEdD8
> OxQzT/ahk7XYRrD0KywCzn6Vd3b7xd+pnBzAJ3TV7lzyXKg97qm6CAAMEdaLNd/3
> 18dKOUmGI5oTRAvTc7Ubdwc4E1qmI4ckBT3QW2LBDOzPaMY6wiLgIA8vETN2bq+S
> vIMN9XDQRbtdwwA+k2fXQUB8b5N+bWdc1/YH5DmuqhKUiaHVCHHBc2K5L8YEydPr
> 0o+MrbwpmlxXjmKQTYFX8L5Wc1DARWECbPIa70TB53uWIxSQdfQQha/Oqd1fMYU0
> H9jPBF0PJHjJMyrTwmvMrZFC9Xi4u3UnKdCOPOCz2DXTttOGsGRsP16so34e9UzR
> DyLD7kR9K/m5djxSYLcIr8mMAfPJ0g/mk1Jyj5Yv9MZVCmFggcfeamirgcvnClxe
> Nhkfyf7SPeq/qpKIVpIOabthtuuoYiH2imnlLCL+TS6qGZYtBkhxlKUjRYMFWm+F
> bTwo3c+FdwOeyWdKn4a6QwIzfaJ70o1EeIYS4MUCyB1TKzcsJWE/t5R0SOqz1SX5
> ofLsn8amwE0dnoCKQhX92sse+sq4ITj3oD5YpehBl4pvzeIs+7LpLHJSVDSFRfwT
> N1Xy/PscHohFgcbfD8dZn/xtxRTN8dz1ysrhwLRBl8zc/tRKYPA=
> =xmQy
> -----END PGP SIGNATURE-----
Though I didn't confirm in-person, Janneke and I have had other
interactions using this key to make me reasonably confident it's their
key.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2017-06-18 20:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-18 5:39 New git signing key for Jan Nieuwenhuizen? Mark H Weaver
2017-06-18 6:00 ` Jan Nieuwenhuizen
2017-06-18 20:50 ` Christopher Allan Webber [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87shix9g12.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=guix-devel@gnu.org \
--cc=janneke@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).