[OE-core] [PATCH 5/5] file: 5.29 -> 5.30

[Manjukumar Harthikote Matha]

> -----Original Message-----
> From: Stefano Babic [mailto:sbabic at denx.de]
> Sent: Monday, March 20, 2017 5:06 PM
> To: Manjukumar Harthikote Matha; Robert Yang; Stefano Babic; openembedded-
> core at lists.openembedded.org
> Subject: Re: [OE-core] [PATCH 5/5] file: 5.29 -> 5.30
>
> On 20/03/2017 12:29, Manjukumar Harthikote Matha wrote:
> >
> >
> >> -----Original Message-----
> >> From: openembedded-core-bounces at lists.openembedded.org
> >> [mailto:openembedded-core-bounces at lists.openembedded.org] On Behalf
> >> Of Robert Yang
> >> Sent: Monday, March 20, 2017 3:14 PM
> >> To: Stefano Babic; openembedded-core at lists.openembedded.org
> >> Subject: Re: [OE-core] [PATCH 5/5] file: 5.29 -> 5.30
> >>
> >> Yes, file's upstream commit ID has changed, Paul has sent a patch for it:
> >>
> >> http://lists.openembedded.org/pipermail/openembedded-core/2017-
> >> March/134261.html
> >>
> >
> > Is it better to use nobranch=1 ?
>
> Is it ? I would prefer to not skip test, just fix the issues.
>
I kind of agree but if this becomes a practice then it will continue to break released versions.

> > Changes in this file.git has broken Morty as well, we used nobranch=1 to resolve
> this issue.
>
> But which revision is taken in your build ? IMHO it is better to fix the revision as Paul
> does in his patch.
>
I agree to use Paul's patch, maybe we should also introduce nobranch=1 was my thinking.

Thanks
Manju

> > I haven't tested this for other released versions of Yocto.
>
> I tested -krogoth, -morty and -master, all of them are broken.
>
> Stefano
>
>
> --
> ====================================================================
> =
> DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
> ====================================================================
> =


This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.