All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH 0/2] Pull request #9
Date: Thu, 19 May 2011 09:30:10 +0200	[thread overview]
Message-ID: <ir2gu2$bq8$1@dough.gmane.org> (raw)
In-Reply-To: <cover.1305756266.git.Martin.Jansa@gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 19-05-11 00:05, Martin Jansa wrote:
> Please merge following 2 patches
> 
> Pull URL: git://gitorious.org/shr/meta-openembedded.git
>   Branch: jama/meta-oe
>   Browse: http://gitorious.org/shr/meta-openembedded/commits/jama/meta-oe

thanks, applied

> 
> Thanks,
>     Martin Jansa <Martin.Jansa@gmail.com>
> ---
> 
> 
> Martin Jansa (2):
>   glib-2.0: use PN instead of glib-2.0 in PACKAGES and FILES
>   glib-2.0: append libffi and python-argparse to
>     DEPENDS_virtclass-native, drop gdbus-serialization test
> 
>  meta-oe/recipes-core/glib-2.0/glib-2.0_git.bb |    4 +++-
>  meta-oe/recipes-core/glib-2.0/glib.inc        |    4 ++--
>  2 files changed, 5 insertions(+), 3 deletions(-)
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFN1McCMkyGM64RGpERAs/8AJ4/brEPwsldBCAAEglfffcNMN4ZTgCfTgCL
iPFIL391ehn+ZSRKwdTtDrs=
=Lr/o
-----END PGP SIGNATURE-----




      parent reply	other threads:[~2011-05-19  7:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-18 22:05 [meta-oe][PATCH 0/2] Pull request #9 Martin Jansa
2011-05-18 22:05 ` [meta-oe][PATCH 1/2] glib-2.0: use PN instead of glib-2.0 in PACKAGES and FILES Martin Jansa
2011-05-18 22:05 ` [meta-oe][PATCH 2/2] glib-2.0: append libffi and python-argparse to DEPENDS_virtclass-native, drop gdbus-serialization test Martin Jansa
2011-05-19  7:30 ` Koen Kooi [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='ir2gu2$bq8$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.