mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: Pending patches/issues before 0.9.15 release?
Date: Sat, 23 Nov 2013 17:02:33 -0500	[thread overview]
Message-ID: <20131123220233.GA24286@brightrain.aerifal.cx> (raw)
In-Reply-To: <20131121013056.GA2128@brightrain.aerifal.cx>

Some updates:

On Wed, Nov 20, 2013 at 08:30:56PM -0500, Rich Felker wrote:
> >From Timo Teräs/fabled/Alpine:
> 
> http://git.alpinelinux.org/cgit/aports/plain/main/musl/1001-add-rfc3678-mcast-structs.patch
> http://git.alpinelinux.org/cgit/aports/plain/main/musl/1002-add-linux-tcp-state-enums.patch
> http://git.alpinelinux.org/cgit/aports/plain/main/musl/1003-add-basic-dns-record-parsing-functions.patch

1001 and 1002 have been committed. 1003 should probably be reviewed
and refactored along with the resolver refactor/overhaul after 1.0.

> >From Michael Forney:
> 
> - simplify strcmp
> - add putspent
> - fix putgrent (missing newline, error handling)
> - dn_expand fix
> - dn_comp stub
> - getopt_long abbreviated options

I'm waiting for minor patch updates for putspent and dn_comp.
getopt_long still needs review. I think the rest have been committed.
There's also a new fgetspent patch that I hope to get included.

> >From Paul Schutte:
> 
> - adding version reporting to ld.so (and elsewhere?)

Still under discussion how best to do it.

> >From nsz's review of pkgsrc failures:
> 
> - getloadavg
> - NO_ADDRESS in netdb.h
> - c_ispeed and c_ospeed in termios
> - termio.h
> - net/if_packet.h
> - ffsl
> - sys/perm.h
> 
> (Note that this is just a selection of topics from the thread which
> looked like they were easy to address on the musl side and which might
> improve practical compatibility, but it's not 100% clear to me that
> they should all be added.)

Some members of the community expressed a sentiment that adding new
things like this should wait until after the release if they're not
critical, even if they're small (like most of the above are).

> And some misc stuff:
> 
> - Revisiting NULL definition

I have not done this yet, but I think it could be done before release
and I'd rather change it now than as a new change in 1.0...

Rich


      parent reply	other threads:[~2013-11-23 22:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-21  1:30 Rich Felker
2013-11-21  9:40 ` Laurent Bercot
2013-11-21 16:39   ` Rich Felker
2013-11-21 16:55     ` Szabolcs Nagy
2013-11-21 19:27     ` Laurent Bercot
2013-11-21 19:44       ` Rich Felker
2013-11-21 20:07         ` Daniel Cegiełka
2013-11-21 20:34           ` Rich Felker
2013-11-21 22:54             ` Laurent Bercot
2013-11-24 11:06         ` zoneinfo file parsing in __tz.c Laurent Bercot
2013-11-24 12:22           ` Szabolcs Nagy
2013-11-21 22:54       ` Pending patches/issues before 0.9.15 release? Szabolcs Nagy
2013-11-21 23:04         ` Laurent Bercot
2013-11-22  0:18           ` Szabolcs Nagy
2013-11-21 23:05         ` Rich Felker
2013-11-21 19:21 ` John Spencer
2013-11-23 22:02 ` Rich Felker [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=20131123220233.GA24286@brightrain.aerifal.cx \
    --to=dalias@aerifal.cx \
    --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).