[yocto] Building BlueZ from git in Yocto

Alexander Kanavin alexander.kanavin at linux.intel.com
Wed Mar 21 08:48:53 PDT 2018


On 03/21/2018 05:47 PM, Alan Martinovic wrote:
> When you say "tagged as backports" are you referring to the Upstream-Status?
> 
> So this is a backport patch:
>      Upstream-Status: Accepted
> [https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=76255f73
>     2d68aef2b90d36d9c7be51a9e1739ce7]
> 
> but these two aren't yet or never will be:
>      Upstream-Status: Submitted
>      Upstream-Status: Denied

See here for explanations:
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines#Patch_Header_Recommendations:_Upstream-Status

In either case, do not rely on Upstream-Status when deciding what to 
drop and what to keep. The only authority is actual code: if it already 
contains the patch (or, in rare cases, resolves the issue in a different 
way), you can drop it. Otherwise you most likely need to keep it, 
rebasing as needed.

Alex



More information about the yocto mailing list