On 07/30/2013 02:46 AM, Burton, Ross wrote:
On 30 July 2013 07:14, Saul Wold 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
pac
On 30 July 2013 11:04, Phil Blundell wrote:
>> 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 p
On Tue, 2013-07-30 at 10:46 +0100, Burton, Ross wrote:
> On 30 July 2013 07:14, Saul Wold 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 con
On 30 July 2013 07:14, Saul Wold 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 defau
Paul, Ross:
Please review (and if needed create new branch) in your morning for an RP
review. This will be RC1 of M3 and we need it to be as solid as possible
as M2 was a bit of a bust!
Please review the build status on the Autobuild, which is currently looking OK,
but not near enough finished.
