On 20 March 2017 at 13:29, Manjukumar Harthikote Matha < manjukumar.harthikote-ma...@xilinx.com> wrote:
> > > > -----Original Message----- > > From: openembedded-core-boun...@lists.openembedded.org > > [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of > > Robert Yang > > Sent: Monday, March 20, 2017 3:14 PM > > To: Stefano Babic; openembedded-core@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 ? > Changes in this file.git has broken Morty as well, we used nobranch=1 to > resolve this issue. > I haven't tested this for other released versions of Yocto. > This is band-aid at best: If you do a "cleanall" to force a new clone the commits likely won't be there anymore. Jussi
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
