From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] clutter-gst: fix patch filename
Date: Tue, 08 Nov 2011 17:33:43 +0000 [thread overview]
Message-ID: <1320773623.10843.83.camel@ted> (raw)
In-Reply-To: <d66b2dd9538139b16969e63a08199cbb25c6cd0c.1320772004.git.josh@linux.intel.com>
On Tue, 2011-11-08 at 09:10 -0800, Joshua Lock wrote:
> Munged the patch filename somehow. Apologies for the noise.
>
> Signed-off-by: Joshua Lock <josh@linux.intel.com>
> ---
> ...{enable_tests-1.8.bb => enable_tests-1.8.patch} | 0
> 1 files changed, 0 insertions(+), 0 deletions(-)
> rename meta/recipes-graphics/clutter/clutter-gst/{enable_tests-1.8.bb => enable_tests-1.8.patch} (100%)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2011-11-08 17:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 17:10 [PATCH 0/1] Fix patch filename in clutter-gst Joshua Lock
2011-11-08 17:10 ` [PATCH 1/1] clutter-gst: fix patch filename Joshua Lock
2011-11-08 17:33 ` 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=1320773623.10843.83.camel@ted \
--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