From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] bluez-dtl1-workaround: deleted
Date: Tue, 12 Jul 2011 15:19:29 +0100 [thread overview]
Message-ID: <1310480369.20015.1062.camel@rex> (raw)
In-Reply-To: <1310054651.6337.94.camel@phil-desktop>
On Thu, 2011-07-07 at 17:04 +0100, Phil Blundell wrote:
> Signed-off-by: Phil Blundell <philb@gnu.org>
> ---
> .../bluez/bluez-dtl1-workaround/02dtl1_cs.sh | 57 ----
> .../bluez/bluez-dtl1-workaround/COPYING.patch | 346 --------------------
> .../bluez/bluez-dtl1-workaround_1.0.bb | 18 -
> 3 files changed, 0 insertions(+), 421 deletions(-)
> delete mode 100644 meta/recipes-connectivity/bluez/bluez-dtl1-workaround/02dtl1_cs.sh
> delete mode 100644 meta/recipes-connectivity/bluez/bluez-dtl1-workaround/COPYING.patch
> delete mode 100644 meta/recipes-connectivity/bluez/bluez-dtl1-workaround_1.0.bb
Merged to master, thanks.
Richard
prev parent reply other threads:[~2011-07-12 14:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 16:04 [PATCH 2/2] bluez-dtl1-workaround: deleted Phil Blundell
2011-07-12 14:19 ` 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=1310480369.20015.1062.camel@rex \
--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