All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] target skeleton definition
Date: Mon, 7 Jun 2010 23:05:41 +0200	[thread overview]
Message-ID: <20100607230541.5f2bf769@surf> (raw)
In-Reply-To: <4c0d5b02.8c4bdf0a.5e33.ffff9c4e@mx.google.com>

Hello Dmytro,

On Mon, 7 Jun 2010 21:06:42 +0300
Dmytro Milinevskyy <milinevskyy@gmail.com> wrote:

> Here's the patch to give posibility to redefine path to the rootfs
> skeleton. Also this patch moves default and busybox skeleton trees
> into fs/skeleton dir.

Thanks for this patch. In general, this is something I intended to do,
so it's great to see patches implementing this.

Personaly, I'd prefer if we could get rid of the "busybox" skeleton
altogether. I think Peter Korsgaard agreed with this decision, but I'll
let him restate his preference here.

If Peter agrees, then the skeleton could be moved to just fs/skeleton/.

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2010-06-07 21:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-07 18:06 [Buildroot] [PATCH] target skeleton definition Dmytro Milinevskyy
2010-06-07 21:05 ` Thomas Petazzoni [this message]
2010-06-07 21:17   ` Peter Korsgaard
2010-06-07 21:37     ` Dmytro Milinevskyy
2010-06-07 22:04     ` Thomas Petazzoni
2010-06-08  6:51       ` Dmytro Milinevskyy
2010-06-08 19:54         ` Dmytro Milinevskyy
2010-06-09  6:39           ` Thomas Petazzoni
2010-06-09  7:06             ` Dmytro Milinevskyy
2010-06-07 21:06 ` Thomas Petazzoni
2010-06-07 21:15   ` Dmytro Milinevskyy

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=20100607230541.5f2bf769@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.