From: Thomas Petazzoni <thomas.petazzoni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
To: Rob Landley <rob-VoJi6FS/r0vR7s880joybQ@public.gmane.org>
Cc: musl-ZwoEplunGu1jrUoiu81ncdBPR1lH4CV8@public.gmane.org,
buildroot-+q+6gMgSsvIBXFe83j6qeQ@public.gmane.org
Subject: Re: [musl] cortex-m support?
Date: Tue, 20 Dec 2016 09:26:00 +0100 [thread overview]
Message-ID: <20161220092600.2ca96088@free-electrons.com> (raw)
In-Reply-To: <48fb6c09-9dcb-e563-dc2d-f30062c5fceb-VoJi6FS/r0vR7s880joybQ@public.gmane.org>
Hello,
On Tue, 20 Dec 2016 01:18:40 -0600, Rob Landley wrote:
> I cc'd the buildroot list, which only has uClibc-based cortex-m support
> at the moment. Why do you suppose I did that?
>
> Did you want me to send it to the uclibc.org mailing list which hasn't
> had a single post this month except your announcement of your fork's
> release? The list where nobody's noticed the chrome browser can't access
> https://lists.uclibc.org (archives, subscription page, etc) for weeks
> now? And yes, I publicized that fact when I noticed it:
Do you realize that the uclibc-ng project has a mailing list? It is
active, people post patches, and they get merged.
I posted patches on this list, they were merged by Waldemar within the
next day or two.
> Your fork clearly hasn't fixed any of the structural issues uClibc
> developed over the years.
Waldemar has fixed the main problem of uClibc: the lack of regular
releases, the lack of a responsive maintainer that merges patches.
Then, from a technical point of view, Waldemar has added new features,
dropped badly supported architectures, cleaned up a lot of things,
improved the test suite, and more. There are probably a tons of other
things to improve in uClibc-ng, but it's just a matter of receiving
contributions: we can no longer blame the lack of maintainership.
[... snip the rest of the text, TLDR ... ]
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-12-20 8:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 5:52 Rob Landley
2016-12-07 15:29 ` Szabolcs Nagy
2016-12-07 15:35 ` Szabolcs Nagy
2016-12-08 0:55 ` Rob Landley
2016-12-08 1:16 ` Rich Felker
2016-12-08 19:10 ` Rob Landley
2016-12-08 21:01 ` Rich Felker
2016-12-08 22:36 ` Rob Landley
2016-12-13 0:29 ` Rob Landley
2016-12-13 1:48 ` Rich Felker
2016-12-20 4:23 ` Rich Felker
2016-12-07 20:19 ` Rob Landley
2016-12-08 21:11 ` Rich Felker
2016-12-09 6:33 ` Rich Felker
[not found] ` <20161208211116.GO1555-C3MtFaGISjmo6RMmaWD+6Sb1p8zYI1N1@public.gmane.org>
2016-12-15 18:34 ` [musl] " Rob Landley
[not found] ` <7bfe2625-725d-d1bb-7177-f2d31ce09e9c-VoJi6FS/r0vR7s880joybQ@public.gmane.org>
2016-12-15 18:51 ` Waldemar Brodkorb
2016-12-20 7:18 ` [Buildroot] " Rob Landley
[not found] ` <48fb6c09-9dcb-e563-dc2d-f30062c5fceb-VoJi6FS/r0vR7s880joybQ@public.gmane.org>
2016-12-20 8:26 ` Thomas Petazzoni [this message]
[not found] ` <20161220092600.2ca96088-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2016-12-20 18:17 ` Rob Landley
2016-12-21 6:18 ` [musl] " Waldemar Brodkorb
[not found] ` <20161221061853.GB2915-zdp6y753eiWHneL7xjqqhBsWhVFi+jh/@public.gmane.org>
2016-12-27 22:03 ` Rob Landley
2016-12-18 0:29 ` Rich Felker
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=20161220092600.2ca96088@free-electrons.com \
--to=thomas.petazzoni-wi1+55scjutkeb57/3fjtnbpr1lh4cv8@public.gmane.org \
--cc=buildroot-+q+6gMgSsvIBXFe83j6qeQ@public.gmane.org \
--cc=musl-ZwoEplunGu1jrUoiu81ncdBPR1lH4CV8@public.gmane.org \
--cc=rob-VoJi6FS/r0vR7s880joybQ@public.gmane.org \
/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).