From: Phil Blundell <pb@pbcl.net>
To: "Burton, Ross" <ross.burton@intel.com>, Saul Wold <sgw@linux.intel.com>
Cc: paul.eggleton@linux.intel.com, openembedded-core@lists.openembedded.org
Subject: Re: [CONSOLIDATED PULL (M3 rc1) 00/26] Needs early review and ACK
Date: Tue, 30 Jul 2013 11:04:06 +0100 [thread overview]
Message-ID: <1375178646.13247.50.camel@phil-desktop.brightsign> (raw)
In-Reply-To: <CAJTo0LZk9HR12mR7nozaE0yZ-DjMPkagf1GvagEeKmkF2i6M9A@mail.gmail.com>
On Tue, 2013-07-30 at 10:46 +0100, Burton, Ross wrote:
> On 30 July 2013 07:14, Saul Wold <sgw@linux.intel.com> wrote:
> > Saul Wold (2):
> > bluez5: Add obex as a PACKAGECONFIG and package seperately
>
> I'm still unsure why this patch was needed. I've nothing against
> splitting out the OBEX functionality and controlling it with a
> packageconfig, but this does disable it by default when before it was
> enabled.
Was that patch ever actually posted to the list? I don't recall seeing
it in my inbox and I can't find it in the ML archive on the web.
p.
next prev parent reply other threads:[~2013-07-30 10:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 6:14 [CONSOLIDATED PULL (M3 rc1) 00/26] Needs early review and ACK Saul Wold
2013-07-30 9:46 ` Burton, Ross
2013-07-30 10:04 ` Phil Blundell [this message]
2013-07-30 13:14 ` Burton, Ross
2013-07-30 14:24 ` Saul Wold
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=1375178646.13247.50.camel@phil-desktop.brightsign \
--to=pb@pbcl.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--cc=ross.burton@intel.com \
--cc=sgw@linux.intel.com \
/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