From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Denis Carikli <denis@eukrea.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] busybox: import the configuration from openembedded.dev
Date: Mon, 5 Sep 2011 17:05:38 +0100 [thread overview]
Message-ID: <201109051705.38793.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <1315237881-14077-1-git-send-email-denis@eukrea.com>
On Monday 05 September 2011 16:51:21 Denis Carikli wrote:
> Without that patch many applets are not build, like for instance
> mdev, which could be necessary for building certain images.
So, leaving aside the problems of replacing the config file with one from an
older version and disabling some options that are currently enabled, the
specific issue of mdev has already been discussed:
http://patches.openembedded.org/patch/5247/
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2011-09-05 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 15:51 [PATCH] busybox: import the configuration from openembedded.dev Denis Carikli
2011-09-05 16:04 ` Phil Blundell
2011-09-05 16:13 ` Eric Bénard
2011-09-05 16:05 ` Paul Eggleton [this message]
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=201109051705.38793.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=denis@eukrea.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