From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Regressions or important missed fixes in 1.1.17?
Date: Sat, 28 Oct 2017 21:53:08 -0400 [thread overview]
Message-ID: <20171029015308.GE1627@brightrain.aerifal.cx> (raw)
Please reply and let me know if there are any regressions in 1.1.17 or
important proposed fixes that didn't make it in, that haven't already
made their way into git master. In order to have a release that's good
to use out of the box without patching, I want to go ahead and package
up a 1.1.18 in the next few days.
Please don't propose anything risky or invasive here; we can start
that again (beginning with several already-pending patches) in the
next release cycle.
Rich
next reply other threads:[~2017-10-29 1:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-29 1:53 Rich Felker [this message]
2017-10-30 9:50 ` Matias Fonzo
2017-10-30 10:39 ` Szabolcs Nagy
2017-10-30 16:44 ` Rich Felker
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=20171029015308.GE1627@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).