From: David Pirotte <david@altosw.be>
To: guile-user@gnu.org, guile-devel <guile-devel@gnu.org>
Subject: Re: Guile-Lib 0.2.4 released
Date: Mon, 14 Nov 2016 06:01:43 -0200 [thread overview]
Message-ID: <20161114060143.676a8ceb@capac> (raw)
In-Reply-To: <20161114055359.269a5acc@capac>
[-- Attachment #1: Type: text/plain, Size: 293 bytes --]
> We are pleased to announce Guile-Lib 0.2.4. This is a maintenance release, the next
> maintena
> ...
> gpg --verify guile-lib-0.2.3.tar.gz.sig
Sorry for the tipo, the signature verification command should obviously be:
gpg --verify guile-lib-0.2.4.tar.gz.sig
David
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2016-11-14 8:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 7:53 Guile-Lib 0.2.4 released David Pirotte
2016-11-14 8:01 ` David Pirotte [this message]
2017-01-19 13:53 ` Guile-Lib 0.2.5 released Matt Wette
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161114060143.676a8ceb@capac \
--to=david@altosw.be \
--cc=guile-devel@gnu.org \
--cc=guile-user@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.
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).