From: Jason Rumney <jasonr@gnu.org>
To: Eric Lilja <mindcooler@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: emacs-20100628 windows binaries
Date: Tue, 29 Jun 2010 07:15:13 +0800 [thread overview]
Message-ID: <87pqzavjem.fsf@home.jasonrumney.net> (raw)
In-Reply-To: <i0b357$frt$1@dough.gmane.org> (Eric Lilja's message of "Mon, 28 Jun 2010 23:10:58 +0200")
Eric Lilja <mindcooler@gmail.com> writes:
> Hmm, after some googling it seems I have to import some key to be able
> to perform the verification. Where can I find it? Sorry if I seem
> dumb, I'm used to verifying against md5sum/sha1sums, not sigs.
The public keys of all GNU uploaders are here:
http://ftp.gnu.org/gnu/gnu-keyring.gpg
prev parent reply other threads:[~2010-06-28 23:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 17:25 emacs-20100628 windows binaries Sean Sieger
2010-06-28 21:10 ` Eric Lilja
2010-06-28 22:11 ` Sean Sieger
2010-06-28 23:15 ` Jason Rumney [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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pqzavjem.fsf@home.jasonrumney.net \
--to=jasonr@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mindcooler@gmail.com \
/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/emacs.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).