From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1 of 5 v3] deprecated handling: introduce BR2_DEPRECATED_SINCE_xxxx_xx
Date: Fri, 10 Jan 2014 07:51:22 +0100 [thread overview]
Message-ID: <52CF986A.9010604@mind.be> (raw)
In-Reply-To: <14cfc9f6c9b34dc82c58.1388764970@argentina>
On 03/01/14 17:02, Thomas De Schampheleire wrote:
> In order to keep better track of when a feature got deprecated, and hence
> when it can be removed, a new set of symbols BR2_DEPRECATED_SINCE_xxxx_xx is
> introduced. These symbols are automatically selected when BR2_DEPRECATED is
> selected, and thus are transparent to the user.
> A deprecated feature will no longer depend on BR2_DEPRECATED directly, but
> rather on the appropriate BR2_DEPRECATED_SINCE_xxxx_xx. If that symbol does
> not yet exist, it has to be created in Config.in.
> When removing a deprecated feature, one should also check whether this was
> the last feature using the BR2_DEPRECATED_SINCE_xxxx_xx symbol, in which
> case the latter can be removed from Config.in.
>
> A followup patch will make sure the overview is added to the list of
> deprecated features in the manual, so that a buildroot core developer can
> easily determine which features to remove in a given development cycle.
>
> Signed-off-by: Thomas De Schampheleire<thomas.de.schampheleire@gmail.com>
At first I was afraid of the complexity added by this patch, but it's
actually not that bad. Therefore:
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
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
next prev parent reply other threads:[~2014-01-10 6:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 16:02 [Buildroot] [PATCH 0 of 5 v3] Introduce new deprecation symbols, and remove squashfs3/ttcp Thomas De Schampheleire
2014-01-03 16:02 ` [Buildroot] [PATCH 1 of 5 v3] deprecated handling: introduce BR2_DEPRECATED_SINCE_xxxx_xx Thomas De Schampheleire
2014-01-04 8:20 ` Thomas De Schampheleire
2014-01-04 8:24 ` Thomas De Schampheleire
2014-01-10 6:51 ` Arnout Vandecappelle [this message]
2014-01-10 14:11 ` Peter Korsgaard
2014-01-03 16:02 ` [Buildroot] [PATCH 2 of 5 v3] manual: clarify handling of deprecated features Thomas De Schampheleire
2014-01-03 16:02 ` [Buildroot] [PATCH 3 of 5 v3] manual package list: add symbol name in table Thomas De Schampheleire
2014-01-10 6:44 ` Arnout Vandecappelle
2014-01-03 16:02 ` [Buildroot] [PATCH 4 of 5 v3] squashfs3: remove deprecated package/rootfs Thomas De Schampheleire
2014-01-10 6:55 ` Arnout Vandecappelle
2014-01-10 14:14 ` Peter Korsgaard
2014-01-03 16:02 ` [Buildroot] [PATCH 5 of 5 v3] ttcp: remove deprecated package 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=52CF986A.9010604@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