From: Thomas De Schampheleire <patrickdepinguin@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1 of 5 v2] manual: clarify handling of deprecated features
Date: Mon, 20 Jan 2014 22:46:06 +0100 [thread overview]
Message-ID: <cb865957be31336fa7be.1390254366@argentina> (raw)
In-Reply-To: <patchbomb.1390254365@argentina>
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
---
v2: resend
docs/manual/appendix.txt | 8 +++++++-
1 files changed, 7 insertions(+), 1 deletions(-)
diff --git a/docs/manual/appendix.txt b/docs/manual/appendix.txt
--- a/docs/manual/appendix.txt
+++ b/docs/manual/appendix.txt
@@ -29,6 +29,12 @@ Deprecated features
-------------------
The following features are marked as _deprecated_ in Buildroot due to
-their status either too old or unmaintained.
+them being either too old or unmaintained. They will be removed at
+some point, so stop using them.
+Each deprecated symbol in kconfig depends on a symbol
++BR2_DEPRECATED_SINCE_xxxx_xx+, which provides an indication of when
+the feature can be removed: features will not be removed within the
+year following deprecation. For example, a symbol depending on
++BR2_DEPRECATED_SINCE_2013_05+ can be removed from 2014.05 onwards.
include::deprecated-list.txt[]
next prev parent reply other threads:[~2014-01-20 21:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 21:46 [Buildroot] [PATCH 0 of 5 v2] Deprecation: clarify manual, remove ttcp and lzma Thomas De Schampheleire
2014-01-20 21:46 ` Thomas De Schampheleire [this message]
2014-01-20 21:46 ` [Buildroot] [PATCH 2 of 5 v2] ttcp: remove deprecated package Thomas De Schampheleire
2014-01-20 21:46 ` [Buildroot] [PATCH 3 of 5 v2] flex: change config text of 'target binary' option Thomas De Schampheleire
2014-01-20 21:46 ` [Buildroot] [PATCH 4 of 5 v2] lzma: remove deprecated target package Thomas De Schampheleire
2014-01-20 21:58 ` Yann E. MORIN
2014-01-21 7:56 ` Thomas De Schampheleire
2014-01-20 21:46 ` [Buildroot] [PATCH 5 of 5 v2] Config.in.legacy: fix misc. problems with libnfc-llcp removal 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=cb865957be31336fa7be.1390254366@argentina \
--to=patrickdepinguin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.