From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH for-2013.11] glibc/eglibc: remove reference to experimental from help text
Date: Tue, 19 Nov 2013 09:10:30 +0100 [thread overview]
Message-ID: <20131119091030.3fde0470@skate> (raw)
In-Reply-To: <1384848007-8853-1-git-send-email-arnout@mind.be>
Dear Arnout Vandecappelle (Essensium/Mind),
On Tue, 19 Nov 2013 09:00:07 +0100, Arnout Vandecappelle
(Essensium/Mind) wrote:
> Since 924b8739da we no longer declare glibc and eglibc support as
> experimental, so it shouldn't be mentioned in the help text anymore.
>
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> ---
> toolchain/toolchain-buildroot/Config.in | 6 ------
> 1 file changed, 6 deletions(-)
Acked-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-11-19 8:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 8:00 [Buildroot] [PATCH for-2013.11] glibc/eglibc: remove reference to experimental from help text Arnout Vandecappelle
2013-11-19 8:10 ` Thomas Petazzoni [this message]
2013-11-19 8:13 ` Peter Korsgaard
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=20131119091030.3fde0470@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