From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] eglibc_2.12.bb: Remove already upstreamed fix-for-make-3.82.diff
Date: Wed, 15 Jun 2011 14:29:58 +0100 [thread overview]
Message-ID: <1308144598.15712.416.camel@rex> (raw)
In-Reply-To: <1308077638-20075-1-git-send-email-raj.khem@gmail.com>
On Tue, 2011-06-14 at 11:53 -0700, Khem Raj wrote:
> This patch is already applied to eglibc 2.12 branch as seen here
> http://www.eglibc.org/cgi-bin/viewcvs.cgi/branches/eglibc-2_12/libc/manual/Makefile?rev=12230&sortby=date&r2=12230&r1=10495
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> .../eglibc/eglibc-2.12/fix-for-make-3.82.diff | 27 --------------------
> meta/recipes-core/eglibc/eglibc_2.12.bb | 3 +-
> 2 files changed, 1 insertions(+), 29 deletions(-)
> delete mode 100644 meta/recipes-core/eglibc/eglibc-2.12/fix-for-make-3.82.diff
Merged to master, thanks.
Richard
prev parent reply other threads:[~2011-06-15 13:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 18:53 [PATCH] eglibc_2.12.bb: Remove already upstreamed fix-for-make-3.82.diff Khem Raj
2011-06-14 19:08 ` Koen Kooi
2011-06-14 19:13 ` Koen Kooi
2011-06-15 13:29 ` Richard Purdie [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=1308144598.15712.416.camel@rex \
--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