Config.in.legacy: update description for developers
authorThomas De Schampheleire <patrickdepinguin+buildroot@gmail.com>
Mon, 2 Sep 2013 20:07:50 +0000 (22:07 +0200)
committerPeter Korsgaard <peter@korsgaard.com>
Sat, 26 Oct 2013 17:04:30 +0000 (19:04 +0200)
commitf8c56f5f6298a31a5440f9ad50d36e4d09b5e0c9
tree4b08f27948fc90804e39fb4b36e7b221e98f1914
parent0764b1cf4573f7fdae9faa280898a7a9950da100
Config.in.legacy: update description for developers

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>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Config.in.legacy