From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: [musl] 1.1.x branch possibility
Date: Sat, 23 May 2020 22:53:00 -0400 [thread overview]
Message-ID: <20200524025259.GM1079@brightrain.aerifal.cx> (raw)
When releasing 1.2.0, I left open the possibility of further releases
in a 1.1.x branch. The libc.threads_minus_1 lock skipping bug is the
first thing to come up that's really big enough to motivate actually
doing such a branch. In practice fairly little is likely to hit it in
practice, but it's enough of an unknown and potential blow-up that we
need to advise patching or upgrade.
Aside from that, there were possibly arch-specific regressions in
1.1.24 on mips, and a few other arch-specific bugs that had been
around for a few release cycles. These would make sense to fix in a
1.1.25, if we do it.
reply other threads:[~2020-05-24 2:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200524025259.GM1079@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.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.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).