Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140721141125.GN17402@brightrain.aerifal.cx>
Date: Mon, 21 Jul 2014 10:11:25 -0400
From: Rich Felker <dalias@...c.org>
To: Glauber Costa <glommer@...udius-systems.com>
Cc: musl@...ts.openwall.com
Subject: Re: [PATCH] implement glibc's glob_pattern_p

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

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.