From: Chris Vine <vine35792468@gmail.com>
To: guile-user@gnu.org, guile-devel@gnu.org
Subject: Re: GNU Guile 3.0.3 released
Date: Mon, 22 Jun 2020 21:50:26 +0100 [thread overview]
Message-ID: <20200622215026.f231e44aea6973830cde8f35@gmail.com> (raw)
In-Reply-To: <87imfk8724.fsf@gnu.org>
On Sun, 21 Jun 2020 23:04:03 +0200
Ludovic Courtès <ludo@gnu.org> wrote:
> We are delighted to announce GNU Guile release 3.0.3, the third bug-fix
> release of the new 3.0 stable series. This release represents 170
> commits by 17 people since version 3.0.2. See the NEWS excerpt that
> follows for full details.
[snip]
This has a libguile so ABI jump from libguile-3.0.so.1 to
libguile-3.0.so.3, which breaks my binaries linked to libguile. Is that
normal for a micro update in the stable release series and if so can
there be some warning in the announcement?
next prev parent reply other threads:[~2020-06-22 20:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-21 21:04 GNU Guile 3.0.3 released Ludovic Courtès
2020-06-22 14:54 ` Jérémy Korwin-Zmijowski
2020-06-22 15:46 ` Dr. Arne Babenhauserheide
2020-06-22 20:50 ` Chris Vine [this message]
2020-06-23 8:05 ` Ludovic Courtès
2020-06-23 9:36 ` Chris Vine
2020-06-24 12:07 ` Andy Wingo
2020-06-24 13:15 ` Ludovic Courtès
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=20200622215026.f231e44aea6973830cde8f35@gmail.com \
--to=vine35792468@gmail.com \
--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).