From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/4] New top-level directory: system
Date: Wed, 5 Sep 2012 11:22:36 +0200 [thread overview]
Message-ID: <20120905112236.09691dad@skate> (raw)
In-Reply-To: <201209042253.05822.yann.morin.1998@free.fr>
Le Tue, 4 Sep 2012 22:53:05 +0200,
"Yann E. MORIN" <yann.morin.1998@free.fr> a ?crit :
> > Even though the skeleton and device tables could have lived in fs/, it
> > would have been strange to have the UART, system hostname and other
> > related options into fs/. A new system/ directory makes more sense.
>
> Agreed. The fs/ sub-dir is now only for all the different rootfs methods.
> I'm not too fond of the 'system' name, but I can see anything else that
> would be fit.
I don't have a strong preference for 'system' either, but that's the
only name I could find that was reasonable. Suggestions welcome.
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:[~2012-09-05 9:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 14:04 [Buildroot] [pull request] Remove Xtensa architecture and target/ directory Thomas Petazzoni
2012-09-04 14:04 ` [Buildroot] [PATCH 1/4] Remove the Xtensa architecture Thomas Petazzoni
2012-09-04 20:48 ` Yann E. MORIN
2012-09-20 20:32 ` Peter Korsgaard
2012-09-04 14:04 ` [Buildroot] [PATCH 2/4] New top-level directory: system Thomas Petazzoni
2012-09-04 20:53 ` Yann E. MORIN
2012-09-05 9:22 ` Thomas Petazzoni [this message]
2012-09-04 14:04 ` [Buildroot] [PATCH 3/4] Remove target/Makefile.in, now useless Thomas Petazzoni
2012-09-04 21:24 ` Yann E. MORIN
2012-09-05 9:23 ` Thomas Petazzoni
2012-09-04 14:04 ` [Buildroot] [PATCH 4/4] Split target/Config.in.arch into multiple Config.in.* in arch/ Thomas Petazzoni
2012-09-04 22:10 ` Yann E. MORIN
2012-09-04 22:37 ` Yann E. MORIN
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=20120905112236.09691dad@skate \
--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.