All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: buildroot@busybox.net
Subject: [Buildroot] [musl] cortex-m support?
Date: Tue, 20 Dec 2016 12:17:10 -0600	[thread overview]
Message-ID: <4f097d57-5ad0-4818-5d4b-9dc4e48c6279@landley.net> (raw)
In-Reply-To: <20161220092600.2ca96088@free-electrons.com>

On 12/20/2016 02:26 AM, Thomas Petazzoni wrote:
> 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?

No, I hadn't noticed. Good to know, I guess?

>> 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.

Bernhard was pretty active in the years right after he became
maintainer. In the long run 10 years of accumulated technical debt was
too much for him, but maybe it'll be different this time.

> 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.

Good luck to him. I have nothing against uclibc-ng the same way I have
nothing against olibc. If I wasn't already regression testing against
glibc, bionic, and musl, I might pay attention to this one.

> [... snip the rest of the text, TLDR ... ]

He asked. :)

Rob

  reply	other threads:[~2016-12-20 18:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <04e5a294-719e-8029-704f-a57d1ec935b0@landley.net>
     [not found] ` <20161208211116.GO1555@brightrain.aerifal.cx>
2016-12-15 18:34   ` [Buildroot] [musl] cortex-m support? Rob Landley
2016-12-15 18:51     ` Waldemar Brodkorb
2016-12-20  7:18       ` Rob Landley
2016-12-20  8:26         ` Thomas Petazzoni
2016-12-20 18:17           ` Rob Landley [this message]
2016-12-20 23:37         ` Arnout Vandecappelle
2016-12-21  3:32           ` Rob Landley
2016-12-21  6:22           ` Baruch Siach
2016-12-21  6:18         ` [Buildroot] [musl] " Waldemar Brodkorb
2016-12-27 22:03           ` Rob Landley

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=4f097d57-5ad0-4818-5d4b-9dc4e48c6279@landley.net \
    --to=rob@landley.net \
    --cc=buildroot@busybox.net \
    /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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.