From: "Ludovic Courtès" <ludo@gnu.org>
To: guile-user@gnu.org, guile-sources@gnu.org
Subject: Guile-Git 0.5.1 released
Date: Tue, 20 Apr 2021 12:34:22 +0200 [thread overview]
Message-ID: <87y2ddcki9.fsf@gnu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1361 bytes --]
Hi!
I’m pleased to announce Guile-Git 0.5.1! Guile-Git is a GNU Guile
library to interact with Git repositories using libgit2.
Latest release:
https://gitlab.com/guile-git/guile-git/-/tags/v0.5.1
Latest release tarball and OpenPGP detached signature:
https://gitlab.com/guile-git/guile-git/uploads/30be542d90619ca844dd3a3ed2e13808/guile-git-0.5.1.tar.gz
https://gitlab.com/guile-git/guile-git/uploads/87ca0d2e30d87b99308aa7eaa5fa755b/guile-git-0.5.1.tar.gz.sig
Repository:
https://gitlab.com/guile-git/guile-git
Reporting issues:
https://gitlab.com/guile-git/guile-git/issues
The ‘v0.5.1’ Git tag and the source code tarball above are signed.
Run ‘git tag -v v0.5.1’ to check the authenticity of your checkout. To
check the authenticity of the tarball, download both the tarball and the
‘.sig’ file and run:
gpg -v guile-git-0.5.1.tar.gz.sig
You may need to retrieve the signing key first:
gpg --keyserver pool.sks-keyservers.net \
--recv-keys 3CE464558A84FDC69DB40CFB090B11993D9AEBB5
* Changes in 0.5.1 (since 0.5.0)
** Bug fix
*** Fix crash when using ‘config-foreach’ or ‘config-fold’
This bug was reported at <https://issues.guix.gnu.org/47808>. It could
lead to segmentation faults in ~tests/config.scm~ while running ~make
check~.
Enjoy!
Ludo’.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 853 bytes --]
next reply other threads:[~2021-04-20 10:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 10:34 Ludovic Courtès [this message]
2021-04-21 22:55 ` Guile-Git 0.5.1 released Aleix Conchillo Flaqué
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=87y2ddcki9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-sources@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).