[meta-intel] [PATCH] bsps: update meta SRCREVs

[Darren Hart]

On 7/24/15, 9:15 AM, "Bruce Ashfield" <bruce.ashfield at windriver.com> wrote:

>On 15-07-24 12:13 PM, Darren Hart wrote:
>> On 7/23/15, 3:59 PM, "Bruce Ashfield" <bruce.ashfield at windriver.com>
>>wrote:
>>
>>> On 2015-07-23 6:56 PM, Burton, Ross wrote:
>>>>
>>>> On 23 July 2015 at 23:45, Bruce Ashfield <bruce.ashfield at windriver.com
>>>> <mailto:bruce.ashfield at windriver.com>> wrote:
>>>>
>>>>      This is only master, and the first tree with no meta branch is
>>>>      the 4.1 kernel tree.
>>>>
>>>>      Existing branches, with their kernel trees, and tools continue to
>>>>      work as they were.
>>>>
>>>>
>>>> Either it's late (it is) or I'm being dumb (quite likely), but why did
>>>> we need to fix the 3.19 srvrevs if it only impacts 4.1 kernels?
>>>
>>> Because the SRC_URI of the main recipe in master now points the
>>> meta name at yocto-kernel-cache (as does 3.14). I needed to do
>>> that, so I could remove the dead code from the tools and put that
>>> into master.
>>>
>>> Some of the main goals here was to reduce complexity, and promote
>>> the sharing of the fragments. So the old stuff goes to the bin :)
>>
>> How will this affect the meta branch of the older kernels in terms of
>> receiving updates that the previous releases, without the infrastructure
>> for the yocto-kernel-cache, can use? Are you going to apply changes to
>> both the old meta branch as well as the new repository until fido is
>>EOL?
>
>Yep. I just apply changes to the meta branches, and update the SRCREVs
>in existing branches, just as I always did.
>
>I always apply changes to both the linux-yocto meta branch and the
>kernel-cache, so if that same kernel recipe was used in master, the
>result is the same.

Got it, thanks Bruce.

-- 
Darren Hart
Intel Open Source Technology Center