From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1 of 9 v3] Config.in.legacy: update description for developers
Date: Thu, 29 Aug 2013 18:19:21 +0200 [thread overview]
Message-ID: <521F7489.4060703@mind.be> (raw)
In-Reply-To: <30166143137061989737.1377781156@argentina>
On 08/29/13 14:59, Thomas De Schampheleire wrote:
> The existing comments in Config.in.legacy are not entirely in-line with
> current practice. The comments implies that BR2_LEGACY should not be set when
> the conversion from old-to-new symbol can be done automatically using the
> appropriate 'select' statements. However, none of the existing legacy options
> does it this way. Moreover, I think it's intentional that the user is notified
> of the change, so that the removal of the legacy options in later buildroot
> versions no longer poses a problem.
> Additionally, the comments now describe how to handle string options.
>
> Signed-off-by: Thomas De Schampheleire<thomas.de.schampheleire@gmail.com>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Regards,
Arnout
[snip]
--
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
next prev parent reply other threads:[~2013-08-29 16:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 12:59 [Buildroot] [PATCH 0 of 9 v3] linux/uboot: add support for custom Mercurial repositories Thomas De Schampheleire
2013-08-29 12:59 ` [Buildroot] [PATCH 1 of 9 v3] Config.in.legacy: update description for developers Thomas De Schampheleire
2013-08-29 16:19 ` Arnout Vandecappelle [this message]
2013-08-29 12:59 ` [Buildroot] [PATCH 2 of 9 v3] Config.in.legacy: update description for users Thomas De Schampheleire
2013-08-29 16:36 ` Arnout Vandecappelle
2013-08-29 12:59 ` [Buildroot] [PATCH 3 of 9 v3] Config.in.legacy: add separator to " Thomas De Schampheleire
2013-08-29 16:37 ` Arnout Vandecappelle
2013-08-29 12:59 ` [Buildroot] [PATCH 4 of 9 v3] Remove redundant dollar signs in Config.in files Thomas De Schampheleire
2013-08-29 12:59 ` [Buildroot] [PATCH 5 of 9 v3] linux: add support for custom Mercurial repository Thomas De Schampheleire
2013-08-29 12:59 ` [Buildroot] [PATCH 6 of 9 v3] u-boot: " Thomas De Schampheleire
2013-08-29 12:59 ` [Buildroot] [PATCH 7 of 9 v3] linux/uboot: line-up repository-related configuration options Thomas De Schampheleire
2013-08-29 12:59 ` [Buildroot] [PATCH 8 of 9 v3] defconfigs: update after rename of custom git repo/version options Thomas De Schampheleire
2013-08-29 12:59 ` [Buildroot] [PATCH 9 of 9 v3] linux: mention 3.x.y kernels in 'custom version' help 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=521F7489.4060703@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