From: Rich Felker <dalias@libc.org>
To: Glauber Costa <glommer@cloudius-systems.com>
Cc: musl@lists.openwall.com
Subject: Re: [PATCH] implement glibc's glob_pattern_p
Date: Mon, 21 Jul 2014 10:11:25 -0400 [thread overview]
Message-ID: <20140721141125.GN17402@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAD-J=zYkxG0hDt_1YqKEHqE4crpUnm70_1PJn+khZGLQJPYHeQ@mail.gmail.com>
On Mon, Jul 21, 2014 at 02:29:59PM +0400, Glauber Costa wrote:
> > they seem to have copied a lot of code from musl, but
> > never said a word about it here.. would be nice to know
> > where they are going with it.. or why they decided to
> > use musl in the first place
> >
>
> I am sorry about that! The decision to use musl was a very early
No need to be sorry. I think nsz just wanted to alert you that there
might be serious bugs that should be fixed if you're going to continue
to use a fork. The WHATSNEW file does a pretty good job of summarizing
important fixes in each release and could be used to find patches to
backport. If your fork is pre-1.0, I would follow the 1.0.x series
WHATSNEW file as long as that branch is maintained since you'll have a
lot less non-bugfix items to sift through than with the 1.1.x series
which has lots of new development in addition to bug fixes.
Rich
next prev parent reply other threads:[~2014-07-21 14:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 9:12 Glauber Costa
2014-07-19 20:11 ` Rich Felker
2014-07-19 23:17 ` Glauber Costa
2014-07-19 23:45 ` Rich Felker
2014-07-20 20:01 ` Thomas Petazzoni
2014-07-21 10:19 ` Glauber Costa
2014-07-20 20:36 ` Szabolcs Nagy
2014-07-21 10:29 ` Glauber Costa
2014-07-21 14:11 ` Rich Felker [this message]
2014-07-21 23:45 ` John Spencer
2014-07-21 14:33 ` Rich Felker
2014-07-21 22:44 ` Glauber Costa
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=20140721141125.GN17402@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=glommer@cloudius-systems.com \
--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).