From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [PATCH] qemu: there is no glflags.patch in the repo, so remove it from SRC_URI
Date: Thu, 31 Mar 2011 15:45:38 +0100 [thread overview]
Message-ID: <1301582738.24596.113.camel@rex> (raw)
In-Reply-To: <1301489300-9174-1-git-send-email-koen@dominion.thruhere.net>
On Wed, 2011-03-30 at 14:48 +0200, koen@dominion.thruhere.net wrote:
> From: Koen Kooi <koen@dominion.thruhere.net>
>
> Probably not the best solution, but I couldn't locate a matching glflags.patch
>
> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
It was accidentally removed by Khem in the qemu upgrade and is still
needed. I've added it back.
Cheers,
Richard
prev parent reply other threads:[~2011-03-31 14:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 12:48 [PATCH] qemu: there is no glflags.patch in the repo, so remove it from SRC_URI koen
2011-03-31 9:52 ` Koen Kooi
2011-03-31 14:45 ` 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=1301582738.24596.113.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=koen@dominion.thruhere.net \
--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