Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2 of 9 v4] Config.in.legacy: update description for users
Date: Tue, 03 Sep 2013 18:50:47 +0200	[thread overview]
Message-ID: <52261367.8040905@mind.be> (raw)
In-Reply-To: <87ob8a54ie.fsf@dell.be.48ers.dk>

On 09/03/13 17:06, Peter Korsgaard wrote:
>>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
>
>
>   Thomas> So far, the only problem I see with this are related to minimal
>   Thomas> defconfigs. In the case (1) above, the minimal defconfig will continue
>   Thomas> to contain the name of the legacy option, and not the name of the new
>   Thomas> option, since the new option is selected by the legacy option. This is
>   Thomas> annoying since it means minimal defconfigs are not progressively
>   Thomas> updated to use the new option name. And this probably makes my entire
>   Thomas> proposal moot.
>
> Damn, yes :/
>
> So people really do need to explictly change to the new option / restart
> make menuconfig.

  I never tried it, but a workaround could be to run olddefconfig before 
any interactive config (menuconfig, nconfig, xconfig, qconfig). 
olddefconfig should be equivalent to saving immediately.

  Regards,
  Arnout


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2013-09-03 16:50 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-02 20:07 [Buildroot] [PATCH 0 of 9 v4] linux/uboot: add support for custom Mercurial repositories Thomas De Schampheleire
2013-09-02 20:07 ` [Buildroot] [PATCH 1 of 9 v4] Config.in.legacy: update description for developers Thomas De Schampheleire
2013-09-02 20:54   ` Thomas Petazzoni
2013-09-03 12:13     ` Thomas De Schampheleire
2013-09-03 16:46       ` Arnout Vandecappelle
2013-10-27  7:24   ` Peter Korsgaard
2013-10-27  8:10     ` Thomas De Schampheleire
2013-09-02 20:07 ` [Buildroot] [PATCH 2 of 9 v4] Config.in.legacy: update description for users Thomas De Schampheleire
2013-09-02 20:55   ` Thomas Petazzoni
2013-09-03  6:16     ` Arnout Vandecappelle
2013-09-03  7:18       ` Thomas Petazzoni
2013-09-03 11:42         ` Thomas De Schampheleire
2013-09-03 11:52           ` Thomas Petazzoni
2013-09-03 15:06             ` Peter Korsgaard
2013-09-03 16:50               ` Arnout Vandecappelle [this message]
2013-09-04  8:33                 ` Thomas De Schampheleire
2013-09-04 16:08                   ` Arnout Vandecappelle
2013-09-04 19:07                     ` Thomas De Schampheleire
2013-09-02 20:07 ` [Buildroot] [PATCH 3 of 9 v4] Config.in.legacy: add separator to " Thomas De Schampheleire
2013-09-02 20:07 ` [Buildroot] [PATCH 4 of 9 v4] Remove redundant dollar signs in Config.in files Thomas De Schampheleire
2013-09-02 20:07 ` [Buildroot] [PATCH 5 of 9 v4] linux: add support for custom Mercurial repository Thomas De Schampheleire
2013-09-02 20:07 ` [Buildroot] [PATCH 6 of 9 v4] u-boot: " Thomas De Schampheleire
2013-09-02 20:07 ` [Buildroot] [PATCH 7 of 9 v4] linux/uboot: line-up repository-related configuration options Thomas De Schampheleire
2013-09-02 20:07 ` [Buildroot] [PATCH 8 of 9 v4] defconfigs: update after rename of custom git repo/version options Thomas De Schampheleire
2013-09-02 20:07 ` [Buildroot] [PATCH 9 of 9 v4] linux: mention 3.x.y kernels in 'custom version' help Thomas De Schampheleire
2013-09-02 21:04   ` Thomas Petazzoni
2013-09-19 19:49 ` [Buildroot] [PATCH 0 of 9 v4] linux/uboot: add support for custom Mercurial repositories Thomas Petazzoni
2013-09-20  9:22   ` Thomas De Schampheleire
2013-09-25 20:12     ` Thomas De Schampheleire

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=52261367.8040905@mind.be \
    --to=arnout@mind.be \
    --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