Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] bison: move remove-gets.patch to BASE_SRC_URI, it's needed for bison-native too if host has (e)glibc-2.16
Date: Sun, 29 Jul 2012 10:17:50 +0100	[thread overview]
Message-ID: <1343553470.16998.20.camel@ted> (raw)
In-Reply-To: <1343506807-24935-1-git-send-email-Martin.Jansa@gmail.com>

On Sat, 2012-07-28 at 22:20 +0200, Martin Jansa wrote:
> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> ---
>  meta/recipes-devtools/bison/bison_2.5.bb |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)


Merged to master, thanks.

Richard




  reply	other threads:[~2012-07-29  9:29 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-08 16:10 [PATCH V2 00/14] eglibc 2.16 Khem Raj
2012-07-08 16:10 ` [PATCH 01/19] mirrors: Add debian archive snapshot mirrors to search list Khem Raj
2012-07-08 16:10 ` [PATCH 02/19] gdb: Replace struct siginfo with proper siginfo_t Khem Raj
2012-07-08 16:10 ` [PATCH 03/19] busybox: Include sys/resource.h for rusage definition Khem Raj
2012-07-08 16:10 ` [PATCH 04/19] coreutils: Fix build with eglibc 2.16 Khem Raj
2012-07-08 16:10 ` [PATCH 05/19] diffutils: " Khem Raj
2012-07-08 16:10 ` [PATCH 06/19] udev: " Khem Raj
2012-07-08 16:10 ` [PATCH 07/19] gettext, m4, augeas, gnutls: Account for removal of gets in " Khem Raj
2012-07-08 16:10 ` [PATCH 08/19] bison: Fix for gets being removed from " Khem Raj
2012-07-28 10:40   ` Jack Mitchell
2012-07-28 18:45     ` Khem Raj
2012-07-28 19:49       ` Jack Mitchell
2012-07-28 20:20         ` [PATCH] bison: move remove-gets.patch to BASE_SRC_URI, it's needed for bison-native too if host has (e)glibc-2.16 Martin Jansa
2012-07-29  9:17           ` Richard Purdie [this message]
2012-07-28 20:24         ` [PATCH 08/19] bison: Fix for gets being removed from eglibc 2.16 Martin Jansa
2012-07-28 20:39           ` Jack Mitchell
2012-07-28 20:52             ` Martin Jansa
2012-07-08 16:10 ` [PATCH 09/19] grub, guile, cpio, tar, wget: Fix gnulib for absense of gets in eglibc Khem Raj
2012-07-08 16:10 ` [PATCH 10/19] boost: Upgrade recipe to 1.50.0 Khem Raj
2012-07-08 16:10 ` [PATCH 11/19] puzzles: Fix checksums Khem Raj
2012-07-08 16:10 ` [PATCH 12/19] valgrind: Fix build with eglibc 2.16 Khem Raj
2012-07-08 16:10 ` [PATCH 13/19] libpam: " Khem Raj
2012-07-08 16:10 ` [PATCH 14/19] gcc-cross-initial.inc: Use BFD ld as default always Khem Raj
2012-07-08 16:10 ` [PATCH 15/19] gcc: Switch to git SRC_URI Khem Raj
2012-07-08 16:10 ` [PATCH 16/19] binutils: Backport the e5500/e6500 patches from mainline Khem Raj
2012-07-08 16:10 ` [PATCH 17/19] gcc: Refresh support for fsl E5500/E6500 Khem Raj
2012-07-08 16:10 ` [PATCH 18/19] qemu: Explicitly add --disable-gl-accel when gl is not enabled Khem Raj
2012-07-08 16:10 ` [PATCH 19/19] eglibc: Add recipes for 2.16 release Khem Raj
2012-07-08 18:47 ` [PATCH V2 00/14] eglibc 2.16 Khem Raj
2012-07-08 21:14 ` Saul Wold
2012-07-09  4:21   ` Khem Raj
2012-07-09  4:26 ` Khem Raj
2012-07-09  9:56   ` Martin Jansa
2012-07-09 16:23     ` Richard Purdie
2012-07-09 22:48   ` Khem Raj

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=1343553470.16998.20.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    /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