From: Thomas De Schampheleire <patrickdepinguin+buildroot@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3 of 9 v4] Config.in.legacy: add separator to description for users
Date: Mon, 02 Sep 2013 22:07:52 +0200 [thread overview]
Message-ID: <390f292e28ee40bd9575.1378152472@argentina> (raw)
In-Reply-To: <patchbomb.1378152469@argentina>
When legacy symbols are selected, the menuconfig shows the explanation for
users, immediately followed by the line "Legacy options removed in 2013.08".
In order to visually keep these apart, we introduce a separator.
Note that a line with all spaces is not correctly shown by menuconfig (the
width will not be kept at 80 characters, so the output is '*** ***').
A dashed line seemed a logical alternative, and with another dashed line on
top, the description becomes a block.
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
---
This patch is pure aesthetics. I kept it as a separate patch so it can be
rejected easily if you don't feel the same way.
v4: no changes
(v3): new patch in this series
Config.in.legacy | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/Config.in.legacy b/Config.in.legacy
--- a/Config.in.legacy
+++ b/Config.in.legacy
@@ -68,6 +68,7 @@ comment "Legacy detected: check the cont
menu "Legacy config options"
if BR2_LEGACY
+comment "----------------------------------------------------"
comment "Your old configuration uses legacy options that no "
comment "longer exist in buildroot, as indicated in the menu "
comment "below. As long as these options stay selected, or in"
@@ -94,6 +95,7 @@ comment "Note: at some point in the futu
comment "options will be removed, and configuration files "
comment "that still have those options set, will fail to "
comment "build, or run, in unpredictable ways. "
+comment "----------------------------------------------------"
endif
###############################################################################
next prev parent reply other threads:[~2013-09-02 20:07 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
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 ` Thomas De Schampheleire [this message]
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=390f292e28ee40bd9575.1378152472@argentina \
--to=patrickdepinguin+buildroot@gmail.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