From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: Preparing for 0.9.13 release
Date: Fri, 23 Aug 2013 20:31:24 +0200 [thread overview]
Message-ID: <20130823183124.GJ30088@port70.net> (raw)
In-Reply-To: <20130823180119.GA11418@brightrain.aerifal.cx>
* Rich Felker <dalias@aerifal.cx> [2013-08-23 14:01:19 -0400]:
> This release is intended to be the last set of major functional
> changes before 1.0. New archs, additional simple legacy functions, and
> other small things can still go in but after 0.9.13 I'd rather hold
> off on big features until post-1.0 so we can instead focus on big
> fixes, testing, etc. and have a solid 1.0 release.
can you wait for long double changes
(i'm cleaning up the freebsd long double bithacks, it will take a few days)
next prev parent reply other threads:[~2013-08-23 18:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 18:01 Rich Felker
2013-08-23 18:31 ` Szabolcs Nagy [this message]
2013-08-25 6:49 ` 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=20130823183124.GJ30088@port70.net \
--to=nsz@port70.net \
--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).