From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] DEVELOPERS: concentrate on uClibc
Date: Tue, 1 May 2018 19:41:18 +0200 [thread overview]
Message-ID: <20180501174118.GE31635@waldemar-brodkorb.de> (raw)
In-Reply-To: <20180428225858.0cd63f20@windsurf>
Hi,
Thomas Petazzoni wrote,
> Hello,
>
> On Sat, 28 Apr 2018 22:35:12 +0200, Waldemar Brodkorb wrote:
> > Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> > ---
> > DEVELOPERS | 5 -----
> > 1 file changed, 5 deletions(-)
> >
> > diff --git a/DEVELOPERS b/DEVELOPERS
> > index 3a4ad60..45a8979 100644
> > --- a/DEVELOPERS
> > +++ b/DEVELOPERS
> > @@ -1952,11 +1952,6 @@ N: Wade Berrier <wberrier@gmail.com>
> > F: package/ngrep/
> >
> > N: Waldemar Brodkorb <wbx@openadk.org>
> > -F: arch/Config.in.m68k
> > -F: arch/Config.in.or1k
> > -F: arch/Config.in.sparc
> > -F: package/glibc/
> > -F: package/mksh/
> > F: package/uclibc/
> > F: package/uclibc-ng-test/
>
> I understand the wish to concentrate on a smaller number of topics.
> However, who is going to take care of the m68k, sparc and OpenRISC
> architecture in Buildroot? I think besides you, not many people were
> interested by those architectures, and they cause fairly frequent
> issues at the toolchain level. Do you have a proposal here ?
I keep responding on the build failure summary mails before a
release. The normal buildroot mails are more informative for me
then the summary for the architectures I subscribed. There I can see
if it is really specific architecture issue or the failure shows up on many
others. And I am always interested in other uClibc-ng toolchain
related issues on other exotic architectures. (microblaze, nios2, ..)
best regards
Waldemar
next prev parent reply other threads:[~2018-05-01 17:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-28 20:35 [Buildroot] [PATCH] DEVELOPERS: concentrate on uClibc Waldemar Brodkorb
2018-04-28 20:58 ` Thomas Petazzoni
2018-05-01 17:41 ` Waldemar Brodkorb [this message]
2018-05-01 19:19 ` Thomas Petazzoni
2018-04-28 21:09 ` Thomas Petazzoni
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=20180501174118.GE31635@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox