[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140620153628.GX179@brightrain.aerifal.cx>
Date: Fri, 20 Jun 2014 11:36:28 -0400
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: Remaining roadmap targets for 1.1.3
On Fri, Jun 20, 2014 at 07:59:57AM -0700, Isaac Dunham wrote:
> On Fri, Jun 20, 2014 at 12:40:32AM -0400, Rich Felker wrote:
> > Here are the not-yet-done primary targets from the roadmap:
> >
> > - Resolver: IDN and result sorting.
> > - Overhaul of if_nameindex and getifaddrs.
> > - Merging fmtmsg. (I have reviewed it now though.)
> v3 has been sent.
Yes, I'm going to look at it now. Thanks!
> > - Merging ports. (Probably not going to happen in this cycle.)
> Which ones? Aarch64, I'm guessing?
Actually or1k (openrisc) was the one I had more hope for getting in
this release cycle, but yes also aarch64. The latter seems rather
stalled and we have several people who've worked on a port but each
left it in a partial state. Not sure what's the best path forward to
finish it.
> > And old items from the post-1.1.1 plans thread:
> > - max_align_t
> > - __xmknod and __sysv_signal patch (ABI compat)
> > - sysconf(_SC_LINE_MAX) issue
> > - errc-family functions
> See [RFC] [v2] Implement errc/warnc family of functions
> from June 13.
> (summary: it may not be needed after all, but here's a patch that
> makes vwarn() call vwarnc(). )
Yes, I'm fine with omitting these if nobody objects.
> > - error.h
> > - reallocarray
> > - explicit_bzero
> I lost track of whether those would be included or not...
Part of the agenda item is determining if they should be included. The
proposal for reallocarray seems to have been accepted by glibc, so
it's a likely candidate for inclusion. explicit_bzero seems like a bad
API (resurrecting the deprecasted bzero vs memset, poorly chosen name,
...) but I guess time will tell. As for error.h, I'm not sufficiently
knowledgable about it to have an opinion yet.
> PS: When I send a revision of a patch, should I send it to the same
> thread or start a new one?
Either is fine, but either way it's nice to put [PATCH v2] or similar
in the subject (really anything to catch my attention that there's a
new patch attached).
Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
