From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] uclibc: Recipes are moved to openembedde-core layer
Date: Mon, 23 May 2011 19:22:21 +0200 [thread overview]
Message-ID: <ire54d$f35$1@dough.gmane.org> (raw)
In-Reply-To: <1306170935-13946-1-git-send-email-raj.khem@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 23-05-11 19:15, raj.khem@gmail.com wrote:
> From: Khem Raj <raj.khem@gmail.com>
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> meta-oe/recipes-core/uclibc/site_config/funcs | 474 --
> meta-oe/recipes-core/uclibc/site_config/headers | 156 -
> meta-oe/recipes-core/uclibc/site_config/types | 21 -
> meta-oe/recipes-core/uclibc/uClibc.distro | 157 -
> meta-oe/recipes-core/uclibc/uclibc-config.inc | 116 -
> .../uclibc/uclibc-git/argp-headers.patch | 581 ---
> .../uclibc/uclibc-git/argp-support.patch | 5189 --------------------
> .../uclibc/uclibc-git/arm/uClibc.machine | 69 -
> .../uclibc/uclibc-git/armeb/uClibc.machine | 53 -
> .../uclibc/uclibc-git/armv5te/uClibc.machine | 76 -
> .../uclibc/uclibc-git/detect-bx-availibility.patch | 75 -
> .../uclibc/uclibc-git/efika/uClibc.machine | 45 -
> .../uclibc/uclibc-git/i386/uClibc.machine | 59 -
> .../uclibc/uclibc-git/i486/uClibc.machine | 62 -
> .../uclibc/uclibc-git/i586/uClibc.machine | 62 -
> .../uclibc/uclibc-git/i686/uClibc.machine | 59 -
> .../uclibc/uclibc-git/include-arm-asm.h.patch | 65 -
> ...so_use_arm_dl_linux_resolve_in_thumb_mode.patch | 21 -
> .../uclibc/uclibc-git/mips64/uClibc.machine | 63 -
> .../uclibc/uclibc-git/mipsel/uClibc.machine | 63 -
> .../uclibc/uclibc-git/nslu2be/uClibc.machine | 73 -
> .../uclibc/uclibc-git/powerpc/uClibc.machine | 46 -
> .../uclibc/uclibc-git/powerpc_copysignl.patch | 107 -
> .../uclibc/uclibc-git/qemuarm/uClibc.machine | 76 -
> .../uclibc/uclibc-git/qemumips/uClibc.machine | 63 -
> .../uclibc/uclibc-git/qemux86/uClibc.machine | 59 -
> .../uclibc-git/remove-eabi-oabi-selection.patch | 91 -
> .../uclibc-git/remove-sub-arch-variants.patch | 215 -
> .../uclibc-git/remove_attribute_optimize_Os.patch | 186 -
> .../uclibc/uclibc-git/reorder-use-BX.patch | 72 -
> .../uclibc/uclibc-git/select-force-thumb.patch | 172 -
> .../uclibc/uclibc-git/sh4/uClibc.machine | 48 -
> .../uclibc-git/transform-eabi-oabi-choice.patch | 71 -
> .../recipes-core/uclibc/uclibc-git/uClibc.distro | 160 -
> .../uclibc/uclibc-git/uclibc-arm-ftruncate64.patch | 13 -
> .../uclibc-git/uclibc_enable_log2_test.patch | 30 -
> .../uclibc/uclibc-git/x86_64/uClibc.machine | 42 -
> meta-oe/recipes-core/uclibc/uclibc-initial_git.bb | 39 -
> meta-oe/recipes-core/uclibc/uclibc.inc | 215 -
> meta-oe/recipes-core/uclibc/uclibc_git.bb | 31 -
> 40 files changed, 0 insertions(+), 9275 deletions(-)
Do you really want to delete them, or do you want keep them to provide a
staging area for changes flowing into oe-core?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFN2pfNMkyGM64RGpERAiO9AKCa3F4M6BQczpV6JNiUv8nrSPPIJwCfbXDc
O9LVvVLwgWHEGvedp8X5A3c=
=s3ms
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-05-23 17:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 17:15 [meta-oe][PATCH] uclibc: Recipes are moved to openembedde-core layer raj.khem
2011-05-23 17:22 ` Koen Kooi [this message]
2011-05-23 18:41 ` 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='ire54d$f35$1@dough.gmane.org' \
--to=koen@dominion.thruhere.net \
--cc=openembedded-devel@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 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.