Cherry-pick request: oe-core rev 2471f9b on branch dizzy

Cherry-pick request: oe-core rev 2471f9b on branch dizzy

[Kang Kai]

[-- Attachment #1: Type: text/plain, Size: 305 bytes --]

Hi Ross,

Would you like to cherry-pick one commit  2471f9b  which is useful from 
branch dizzy to master, please?

http://git.openembedded.org/openembedded-core/commit/meta/recipes-devtools/valgrind?h=dizzy&id=2471f9b32a96bcb64a5a04d53456818cad57befe

Thanks.

-- 
Regards,
Neil | Kai Kang


[-- Attachment #2: Type: text/html, Size: 868 bytes --]

Re: Cherry-pick request: oe-core rev 2471f9b on branch dizzy

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 356 bytes --]

On 1 July 2015 at 11:09, Kang Kai <Kai.Kang@windriver.com> wrote:

> Would you like to cherry-pick one commit  2471f9b  which is useful from
> branch dizzy to master, please?
>

How did that get into dizzy without going through master... :/

This doesn't apply to master anymore - would you be able to port and verify
it works correctly?

Ross

[-- Attachment #2: Type: text/html, Size: 802 bytes --]

Re: Cherry-pick request: oe-core rev 2471f9b on branch dizzy

[Kang Kai]

[-- Attachment #1: Type: text/plain, Size: 575 bytes --]

On 2015年07月01日 18:37, Burton, Ross wrote:
>
> On 1 July 2015 at 11:09, Kang Kai <Kai.Kang@windriver.com 
> <mailto:Kai.Kang@windriver.com>> wrote:
>
>     Would you like to cherry-pick one commit 2471f9b  which is useful
>     from branch dizzy to master, please?
>
>
> How did that get into dizzy without going through master... :/
>
> This doesn't apply to master anymore - would you be able to port and 
> verify it works correctly?

OK. I'll send the which is rebased on master.

Thanks.

--Kai

>
> Ross


-- 
Regards,
Neil | Kai Kang


[-- Attachment #2: Type: text/html, Size: 1977 bytes --]

Re: Cherry-pick request: oe-core rev 2471f9b on branch dizzy

[Paul Eggleton]

On Wednesday 01 July 2015 11:37:22 Burton, Ross wrote:
> On 1 July 2015 at 11:09, Kang Kai <Kai.Kang@windriver.com> wrote:
> > Would you like to cherry-pick one commit  2471f9b  which is useful from
> > branch dizzy to master, please?
> 
> How did that get into dizzy without going through master... :/

I'd like to state for the record that in the absence of the submitter taking 
care of it, the responsibility rests with stable branch maintainers to ensure 
that any patch taken into the branch they maintain has been merged into all 
newer branches first, unless it isn't applicable to those branches. It's a 
pain, but we don't have any automatic mechanism to pick up this situation so 
for now we rely on it being done manually. 

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre