mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Pending patches & other changes
Date: Fri, 1 May 2015 13:42:59 -0400	[thread overview]
Message-ID: <20150501174259.GC17573@brightrain.aerifal.cx> (raw)
In-Reply-To: <20150428034820.GA28803@brightrain.aerifal.cx>

On Mon, Apr 27, 2015 at 11:48:20PM -0400, Rich Felker wrote:
> Here is a list of patches I'm aware of that have been sent to the list
> that I haven't yet applied or rejected:
> 
> [PATCH] generate debug_frame info for __syscall_cp_asm (i386) so gdb can get backtrace
> [PATCH] fmtmsg: verify that label is in the correct format.
> [PATCH] replace 'hlt' by 'ud2' in i386/x32/x86_64 a_crash implementations
> [PATCH] conforming strverscmp() implementation
> 
> There are also a few patches from nsz on the radar:
> 
> http://port70.net/~nsz/musl/0001-add-IPTOS_CLASS_-macros-to-netinet-ip.h.patch
> http://port70.net/~nsz/musl/0001-complex-fix-ctanh-0-i-nan-and-ctanh-0-i-inf.patch

I applied these two.

> http://port70.net/~nsz/musl/0001-inet_pton-clean-up.patch

I suspect this should be done but I want to review it well and haven't
gotten around to that yet. Let's look again after release.

> and the BRE extensions that are still under discussion, and possibly

Since adding these now would be a big committment to keep them I think
we should hold off until/unless there's evidence that they're widely
needed. I'd prefer getting apps fixed but if it's a recurring headache
for users maybe we should just add them.

> some cleanup of some always-false null checks in the failure path of
> regcomp.

This is just cleanup and I want to be sure it's correct before doing
it, so let's look again after release.

Rich


      parent reply	other threads:[~2015-05-01 17:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-28  3:48 Rich Felker
2015-04-28  9:43 ` Szabolcs Nagy
2015-04-28 13:46   ` Rich Felker
2015-04-28 13:55     ` Szabolcs Nagy
2015-05-01 17:42 ` 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=20150501174259.GC17573@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --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).