From: John Spencer <maillist-musl@barfooze.de>
To: musl@lists.openwall.com
Subject: Re: Issues remaining for release?
Date: Tue, 11 Sep 2012 22:13:59 +0200 [thread overview]
Message-ID: <504F9B87.7010109@barfooze.de> (raw)
In-Reply-To: <20120911064545.GQ27715@brightrain.aerifal.cx>
On 09/11/2012 08:45 AM, Rich Felker wrote:
> Hi all,
>
> Are there any major issues left that should be resolved before a
> release?
no
> Since many of these are fairly invasive, it'd be great to have some
> help testing for regressions.
>
no regressions detected while doing a full sabotage amd64 build with
latest git.
since the mips and arm port was never widely used, i think it's safe to
get out a release.
(doing a full build on arm would take about 2 days, so i refrained from
doing so for the moment.)
prev parent reply other threads:[~2012-09-11 20:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 6:45 Rich Felker
2012-09-11 20:13 ` John Spencer [this message]
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=504F9B87.7010109@barfooze.de \
--to=maillist-musl@barfooze.de \
--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).