On Fri, Nov 16, 2018 at 7:51 AM Raphael Kubo da Costa <raphael.kubo.da.co...@intel.com> wrote: > > akuster808 <akuster...@gmail.com> writes: > > > On 11/14/18 5:23 AM, Raphael Kubo da Costa wrote: > > > >> From: Khem Raj <raj.k...@gmail.com> > >> > >> exposed by glibc 2.28 for details see > >> https://lists.gnu.org/r/bug-gnulib/2018-03/msg00000.html > >> > >> (From OE-Core rev: acca7f964bf9c21f3777085563a7928b8246f17f) > >> > >> Signed-off-by: Khem Raj <raj.k...@gmail.com> > >> Signed-off-by: Richard Purdie <richard.pur...@linuxfoundation.org> > >> Signed-off-by: Raphael Kubo da Costa <raphael.kubo.da.co...@intel.com> > > > > in in stable/rocko-nmut. Odd thing it, this is not in patchwork but the > > sumo version is. > > Thanks. I need a few more patches to get host tools to build here on > Fedora 29, but now I'm even more confused as to where to send them :-) > > What's the relationship between the -next, -nmut and -nmut2 branches in > Yocto's poky-contrib? How do they interact with oe-core's -next > branches? And what's the process for merging them into the actual stable > branches?
they are staging private branches used by maintainers. Eventually they should show up in <release>-next and then into <release> branch > -- > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
