mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Denys Vlasenko <vda.linux@googlemail.com>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: busybox <busybox@busybox.net>, musl <musl@lists.openwall.com>
Subject: Re: bbox: musl versus uclibc
Date: Wed, 16 Aug 2017 15:25:20 +0200	[thread overview]
Message-ID: <CAK1hOcN_uD7zaPFwsq2TZ9E=6+RzzsjRfq8WNReqifJWToS45g@mail.gmail.com> (raw)
In-Reply-To: <20170816143428.5845c87c@windsurf>

On Wed, Aug 16, 2017 at 2:34 PM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> Hello,
>
> On Mon, 14 Aug 2017 12:59:41 -0500, wdlkmpx wrote:
>
>> I'm sure there was plenty of people willing to contribute  to uclibc,
>> there is even an updated fork.
>>
>> The project has been badly managed.. thats the only reason i can think
>> of for this situation  to happen
>
> uClibc-ng is alive at https://uclibc-ng.org/. Regular releases
> (actually more regular than musl in recent months!), updated web site,
> responsive maintainer, lots of cleanup in the code base, and QA effort.
>
> So saying that uClibc is dead is completely incorrect.

These "ng" names are not the best idea.

Maybe uclibc-ng can just supersede uclibc?

We can give www.uclibc.org domain (or the server itself) to it.

  parent reply	other threads:[~2017-08-16 13:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-14 17:43 Denys Vlasenko
2017-08-14 17:59 ` wdlkmpx
2017-08-16 12:34   ` Thomas Petazzoni
2017-08-16 12:57     ` Jorge Almeida
2017-08-17  4:29       ` Waldemar Brodkorb
2017-08-16 13:25     ` Denys Vlasenko [this message]
2017-08-16 13:36       ` Thomas Petazzoni
2017-08-17  4:35         ` [musl] " Waldemar Brodkorb
2017-08-14 18:18 ` Emmanuel Deloget
2017-08-14 18:48 ` Rich Felker
2017-08-14 22:13   ` Denys Vlasenko

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='CAK1hOcN_uD7zaPFwsq2TZ9E=6+RzzsjRfq8WNReqifJWToS45g@mail.gmail.com' \
    --to=vda.linux@googlemail.com \
    --cc=busybox@busybox.net \
    --cc=musl@lists.openwall.com \
    --cc=thomas.petazzoni@free-electrons.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).