From: Marcin Juszkiewicz <marcin@juszkiewicz.com.pl>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] busybox-1.21.1/defconfig: disable rfkill
Date: Mon, 29 Jul 2013 13:09:41 +0200 [thread overview]
Message-ID: <51F64D75.60601@juszkiewicz.com.pl> (raw)
In-Reply-To: <CAOMwXhPMi6cG858ZX9r+c310hdvGMRbNKLYEadyr0e9GVUuTqw@mail.gmail.com>
W dniu 29.07.2013 12:44, Laszlo Papp pisze:
> OK, I give up the contribution. I really cannot collaborate with
> people who think it is acceptable to break *many* users' life for the
> whole project without being able to use anything in favor of a very
> limited (!) people with only two (!) applications.
Stop being closed minded. OpenEmbedded provides many options for doing
alterations and you got some suggestions in this thread how to make you
happy without breaking setup for other people.
If your toolchain is more then 4 years old then maybe stick with older
versions of OE as well?
Or just update linux-libc-headers part of toolchain and be happy with
it? But it would require you to rebuild everything to check does it
builds...
Or do one simple change in your own layer to disable this config option?
This would take you just 5 minutes and provide compatibility with
probably even 2.4 kernels.
next prev parent reply other threads:[~2013-07-29 11:10 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 7:16 [PATCH] busybox-1.21.1/defconfig: disable rfkill Laszlo Papp
2013-07-29 7:20 ` Paul Barker
2013-07-29 7:22 ` Laszlo Papp
2013-07-29 10:00 ` Phil Blundell
2013-07-29 10:01 ` Laszlo Papp
2013-07-29 10:20 ` Phil Blundell
2013-07-29 10:22 ` Laszlo Papp
2013-07-29 10:30 ` Laszlo Papp
2013-07-29 10:38 ` Phil Blundell
2013-07-29 10:42 ` Laszlo Papp
2013-07-29 10:46 ` Paul Barker
2013-07-29 10:48 ` Laszlo Papp
2013-07-29 11:05 ` Laszlo Papp
2013-07-29 10:46 ` Burton, Ross
2013-07-29 10:50 ` Laszlo Papp
2013-07-29 10:35 ` Phil Blundell
2013-07-29 10:37 ` Laszlo Papp
2013-07-29 12:18 ` Laszlo Papp
2013-07-29 12:20 ` Laszlo Papp
2013-07-29 13:34 ` Bernhard Reutner-Fischer
2013-07-29 13:34 ` Laszlo Papp
2013-07-29 15:42 ` Bernhard Reutner-Fischer
2013-07-30 15:55 ` Laszlo Papp
2013-07-30 16:10 ` Phil Blundell
2013-07-30 16:21 ` Burton, Ross
2013-07-31 11:13 ` Laszlo Papp
2013-07-29 10:42 ` Burton, Ross
2013-07-29 10:44 ` Laszlo Papp
2013-07-29 11:09 ` Marcin Juszkiewicz [this message]
2013-07-29 11:14 ` Laszlo Papp
2013-07-31 22:36 ` Khem Raj
[not found] ` <CAOMwXhMPmoFo+bYz9NAijJevWvizNFm0rsbVn1fPNHCS4Kf7yw@mail.gmail.com>
2013-08-13 7:32 ` Laszlo Papp
2013-08-13 7:33 ` Laszlo Papp
2013-08-13 9:48 ` Burton, Ross
2013-08-13 9:52 ` Laszlo Papp
2013-08-13 9:55 ` Laszlo Papp
2013-08-13 9:58 ` Burton, Ross
2013-08-13 10:00 ` Laszlo Papp
2013-08-13 10:17 ` Phil Blundell
2013-08-13 10:14 ` Jack Mitchell
2013-08-13 10:19 ` Laszlo Papp
2013-08-13 10:35 ` Jack Mitchell
2013-08-13 10:39 ` Laszlo Papp
2013-08-14 8:35 ` Fathi Boudra
-- strict thread matches above, loose matches on Subject: below --
2013-07-28 22:31 Laszlo Papp
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=51F64D75.60601@juszkiewicz.com.pl \
--to=marcin@juszkiewicz.com.pl \
--cc=openembedded-core@lists.openembedded.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox