From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/4] Make savedefconfig save to a configured file.
Date: Tue, 05 Feb 2013 21:43:40 +0100 [thread overview]
Message-ID: <87vca6o5j7.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <41e27bc2d2881606d1da299f6056d24bc9d34e78.1360084128.git.arnout@mind.be> (Arnout Vandecappelle's message of "Tue, 5 Feb 2013 18:16:02 +0100")
>>>>> "Arnout" == Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> writes:
Arnout> From: "Arnout Vandecappelle (Essensium/Mind)" <arnout@mind.be>
Arnout> Store BR2_DEFCONFIG in .config, and use it to update the
Arnout> original input defconfig file after updating the configuration.
Arnout> When a config is created by using the BR2_DEFCONFIG=... option,
Arnout> this is saved in the .config file; later runs of savedefconfig
Arnout> will update that same location.
Committed with a minor fix (see below) - Thanks.
Arnout> +called +defconfig+. If you want to save it in another place, update set
s/update set/change/
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2013-02-05 20:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 17:15 [Buildroot] [pull request v4] Pull request for branch arnout-update-config Arnout Vandecappelle
2013-02-05 17:15 ` [Buildroot] [PATCH 1/4] manual: add section about storing the configuration Arnout Vandecappelle
2013-02-05 20:04 ` Peter Korsgaard
2013-02-05 17:16 ` [Buildroot] [PATCH 2/4] target/generic: add filesystem overlay option Arnout Vandecappelle
2013-02-05 20:37 ` Peter Korsgaard
2013-02-05 21:28 ` Arnout Vandecappelle
2013-02-05 17:16 ` [Buildroot] [PATCH 3/4] busybox: busybox-update-config should depend on busybox-configure Arnout Vandecappelle
2013-02-05 20:38 ` Peter Korsgaard
2013-02-05 17:16 ` [Buildroot] [PATCH 4/4] Make savedefconfig save to a configured file Arnout Vandecappelle
2013-02-05 20:43 ` Peter Korsgaard [this message]
2013-02-06 14:15 ` Gustavo Zacarias
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=87vca6o5j7.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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