From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: openembedded-core@www.linuxtogo.org,
Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [PATCH] gettext: fix ERROR: QA Issue: gettext rdepends on gettext-dev
Date: Tue, 05 Jul 2011 11:28:11 +0100 [thread overview]
Message-ID: <1309861691.20015.683.camel@rex> (raw)
In-Reply-To: <1309514503-9364-1-git-send-email-koen@dominion.thruhere.net>
On Fri, 2011-07-01 at 12:01 +0200, Koen Kooi wrote:
> This was fixed in 2008 already, see http://dominion.thruhere.net/koen/cms/the-testlab-strikes-again but regressed during the 0.16.x -> 0.18.x update. Strangely enough the comment was kept.
>
> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
> ---
> meta/recipes-core/gettext/gettext_0.18.1.1.bb | 8 +++++++-
> 1 files changed, 7 insertions(+), 1 deletions(-)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2011-07-05 10:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 10:01 [PATCH] gettext: fix ERROR: QA Issue: gettext rdepends on gettext-dev Koen Kooi
2011-07-05 10:28 ` 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=1309861691.20015.683.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-core@www.linuxtogo.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