From: Phil Blundell <philb@gnu.org>
To: Darren Hart <dvhart@linux.intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] busybox: Include setsid and cttyhack in defconfig
Date: Mon, 18 Jun 2012 12:35:04 +0100 [thread overview]
Message-ID: <1340019305.14857.147.camel@phil-desktop> (raw)
In-Reply-To: <4FDCB690.8090004@linux.intel.com>
On Sat, 2012-06-16 at 09:38 -0700, Darren Hart wrote:
> With the above goal in mind, can you accept either of my proposed
> patches as an interim solution? Either as an added tiny DISTRO_FEATURE
> or as a simple addition to the defconfig? I do believe these two
> features are useful beyond poky-tiny.
Well, obviously it isn't my place to accept or reject your patch; one of
the oe-core maintainers would have to make that decision. But,
personally, given a choice between those two options I would prefer the
latter.
However, I do still think that the best interim approach is just to
provide a suitable, complete defconfig file in whatever layer contains
poky-tiny. This doesn't need to involve splitting poky-tiny into its
own layer, doesn't require any extra tooling in oe-core in the short
term, and doesn't necessarily even need to involve a .bbappend (although
it would probably be easiest if it did).
p.
next prev parent reply other threads:[~2012-06-18 11:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 22:39 [PATCH 0/1] busybox: Include setsid and cttyhack in defconfig Darren Hart
2012-06-15 22:40 ` [PATCH 1/1] " Darren Hart
2012-06-15 22:56 ` Darren Hart
2012-06-16 16:18 ` Phil Blundell
2012-06-16 16:38 ` Darren Hart
2012-06-16 17:47 ` Khem Raj
2012-06-16 21:47 ` Darren Hart
2012-06-17 2:41 ` Koen Kooi
2012-06-17 21:14 ` Paul Eggleton
2012-06-17 21:55 ` Khem Raj
2012-06-18 5:00 ` Koen Kooi
2012-06-18 7:58 ` Paul Eggleton
2012-06-18 9:26 ` Koen Kooi
2012-06-18 10:43 ` Paul Eggleton
2012-06-18 11:35 ` Phil Blundell [this message]
2012-06-18 14:28 ` Darren Hart
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=1340019305.14857.147.camel@phil-desktop \
--to=philb@gnu.org \
--cc=dvhart@linux.intel.com \
--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