From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] Add option to copy config file to rootfs
Date: Thu, 31 Jul 2014 23:50:47 +0200 [thread overview]
Message-ID: <20140731235047.5b95e826@free-electrons.com> (raw)
In-Reply-To: <1406820398-2105-1-git-send-email-nroach44@gmail.com>
Dear Nathaniel Roach,
On Thu, 31 Jul 2014 23:26:38 +0800, Nathaniel Roach wrote:
> BR2_CONFIG_COPY copies the config file to /etc/buildroot.config
> as 0600 during target-finalize after overlay copy, but before
> post-build script install.
>
> ---
> Changes v1 to v2
> - Corrected wording of config helper message (Thomas De Schampheleire)
> - Moved order in menu to reflect actual order of the operation
> ---
> Makefile | 4 ++++
> system/Config.in | 11 +++++++++++
> 2 files changed, 15 insertions(+)
Thanks for the proposal, but apparently there's no really a consensus
around it and there's a very simple way to do the same using a
post-build script, so I've marked the patch as Rejected in patchwork.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-07-31 21:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 15:26 [Buildroot] [PATCH v2] Add option to copy config file to rootfs Nathaniel Roach
2014-07-31 17:16 ` Yann E. MORIN
2014-07-31 17:55 ` Thomas De Schampheleire
2014-07-31 18:17 ` Thomas Petazzoni
2014-07-31 18:40 ` Thomas De Schampheleire
2014-07-31 21:37 ` Yann E. MORIN
2014-08-01 4:45 ` Thomas De Schampheleire
2014-07-31 17:19 ` Matthew Weber
2014-07-31 21:50 ` Thomas Petazzoni [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=20140731235047.5b95e826@free-electrons.com \
--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