From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] pthread-stubs: rename to xlib_libpthread-stubs
Date: Tue, 08 Jan 2013 23:51:41 +0100 [thread overview]
Message-ID: <50ECA2FD.5020208@mind.be> (raw)
In-Reply-To: <20130108232920.6676165c@skate>
On 01/08/13 23:29, Thomas Petazzoni wrote:
> Dear Arnout Vandecappelle,
>
> On Tue, 08 Jan 2013 22:37:10 +0100, Arnout Vandecappelle wrote:
>
>> - There would be a comment that this is a legacy option from 2011.11;
>
> Ok, so, something like:
>
> #
> # Legacy options from 2012.11
> #
ACK
>
>> - The BR2_LEGACY_CHECK_2012_11 is updated to BR2_LEGACY_CHECK_2013_02 so
>> that it is re-enabled (but this can be done just prior to the release, of
>> course).
>
> I am not sure to fully understand the idea in Config.in.legacy. What
> happens if someone upgrades from 2012.08 to 2013.02 (i.e, skips the
> 2012.11 version) ?
When an old .config contains a legacy symbol, you can easily get rid of
it by de-selecting the "Check for legacy options" menuconfig. But of
course, it will stay de-selected the next time you upgrade buildroot and
so there will be no more checks for legacy options... To work around
that, we should change the name of the menuconfig symbol with every
release. It doesn't really matter what name we give it, as long as it
changes.
If someone upgrades from 2012.11 to 2015.11, it will still be a
different symbol so it will default to y again.
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
prev parent reply other threads:[~2013-01-08 22:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-05 12:26 [Buildroot] [git commit] pthread-stubs: rename to xlib_libpthread-stubs Peter Korsgaard
2013-01-08 21:37 ` Arnout Vandecappelle
2013-01-08 22:29 ` Thomas Petazzoni
2013-01-08 22:51 ` Arnout Vandecappelle [this message]
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=50ECA2FD.5020208@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