All of lore.kernel.org
 help / color / mirror / Atom feed
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 22:37:10 +0100	[thread overview]
Message-ID: <50EC9186.7050802@mind.be> (raw)
In-Reply-To: <20130105124707.668AD9A64B@busybox.osuosl.org>

  Peter, Thomas,

On 01/05/13 13:26, Peter Korsgaard wrote:
[snip]
> diff --git a/Config.in.legacy b/Config.in.legacy
> index 7ddc6ea..4770c94 100644
> --- a/Config.in.legacy
> +++ b/Config.in.legacy
> @@ -70,4 +70,12 @@ config BR2_PACKAGE_INPUT_TOOLS_EVTEST
>   	help
>   	  The evtest program from input-tools is now a separate package.
>
> +config BR2_PACKAGE_PTHREAD_STUBS
> +	bool "pthread-stubs option has been renamed"
> +	select BR2_LEGACY
> +	select BR2_PACKAGE_XLIB_LIBPTHREAD_STUBS
> +	help
> +	  For consistency reason, the pthread-stubs package has been
> +	  renamed to xlib_libpthread-stubs.
> +
>   endif

  The intention was that:

- There would be a comment that this is a legacy option from 2011.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).

  Regards,
  Arnout

[snip]
-- 
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

  reply	other threads:[~2013-01-08 21:37 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 [this message]
2013-01-08 22:29   ` Thomas Petazzoni
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=50EC9186.7050802@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 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.