From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] pthread-stubs: rename to xlib_libpthread-stubs
Date: Tue, 8 Jan 2013 23:29:20 +0100 [thread overview]
Message-ID: <20130108232920.6676165c@skate> (raw)
In-Reply-To: <50EC9186.7050802@mind.be>
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
#
> - 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) ?
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-01-08 22:29 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 [this message]
2013-01-08 22:51 ` Arnout Vandecappelle
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=20130108232920.6676165c@skate \
--to=thomas.petazzoni@free-electrons.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