From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit master 1/1] initramfs: update help text
Date: Mon, 28 Jun 2010 17:21:40 +0200 [thread overview]
Message-ID: <20100628172140.20a96bc0@surf> (raw)
In-Reply-To: <i0ae60$t0c$1@dough.gmane.org>
On Mon, 28 Jun 2010 15:13:04 +0000 (UTC)
Grant Edwards <grant.b.edwards@gmail.com> wrote:
> I still don't understand why one can build a cpio archive without
> building a kernel, but in order to create a list of what's in the cpio
> archive a kernel must be built.
I think I've already said that it was just one choice to solve bug
#2119, but that there was also other ways to solve the same bug (for
example by enabling the dependency from initramfs to the kernel only
when the kernel build is enabled).
So there's nothing to understand: it was one way to fix the bug,
and it later turned out that this way was too restrictive and that the
bug must therefore be fixed another way. Which will be done.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-06-28 15:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-26 5:44 [Buildroot] [git commit master 1/1] initramfs: update help text Peter Korsgaard
2010-06-26 14:21 ` Grant Edwards
2010-06-26 16:48 ` Thomas Petazzoni
2010-06-27 3:46 ` Grant Edwards
2010-06-26 19:13 ` Peter Korsgaard
2010-06-27 3:46 ` Grant Edwards
2010-06-27 6:22 ` Peter Korsgaard
2010-06-27 7:30 ` Thomas Petazzoni
2010-06-27 13:46 ` Grant Edwards
2010-06-27 20:02 ` Peter Korsgaard
2010-06-27 20:10 ` Peter Korsgaard
2010-06-28 0:46 ` Grant Edwards
2010-06-28 15:13 ` Grant Edwards
2010-06-28 15:21 ` Thomas Petazzoni [this message]
2010-06-27 13:42 ` Grant Edwards
2010-06-27 18:57 ` Thomas Petazzoni
2010-06-28 0:39 ` Grant Edwards
2010-06-28 7:22 ` Peter Korsgaard
2010-06-27 20:08 ` Peter Korsgaard
2010-06-28 1:03 ` Grant Edwards
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=20100628172140.20a96bc0@surf \
--to=thomas.petazzoni@free-electrons.com \
--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