From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: Releasing 0.8.4?
Date: Sat, 21 Jan 2012 12:51:19 +0100 [thread overview]
Message-ID: <20120121115119.GW31975@port70.net> (raw)
In-Reply-To: <20120121010720.GA8353@brightrain.aerifal.cx>
* Rich Felker <dalias@aerifal.cx> [2012-01-20 20:07:20 -0500]:
> Anything critical that should be addressed before releasing current
> git as 0.8.4? I figure it's been in a "stable" (hiatus) state long
> enough that it should be good, but if not I'd like to hear about the
> problems sooner rather than later. :-)
i reported a bug about the CHUNK_SIZE macro of malloc
there is an old related FIXME comment in malloc.c
you haven't replied my mail if that can be resolved
with the found bug
imho that if(0) can be eliminated
but i don't quite understand the
algorithm as much as you do..
next prev parent reply other threads:[~2012-01-21 11:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 1:07 Rich Felker
2012-01-21 11:51 ` Szabolcs Nagy [this message]
2012-01-21 13:08 ` Rich Felker
2012-01-21 13:47 ` Szabolcs Nagy
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=20120121115119.GW31975@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).