[OE-core] [rocko][PATCH] m4: Workaround gnulib's fseeko.c implementation

Burton, Ross ross.burton at intel.com
Fri Nov 16 17:22:05 UTC 2018

On Fri, 16 Nov 2018 at 17:16, Kubo Da Costa, Raphael
<raphael.kubo.da.costa at intel.com> wrote:
> On Fri, 2018-11-16 at 09:05 -0800, Khem Raj wrote:
> > On Fri, Nov 16, 2018 at 7:51 AM Raphael Kubo da Costa
> > <raphael.kubo.da.costa at intel.com> wrote:
> > > 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
> Right, and how do I know which and whose branch(es) to check for before
> sending a backport (or even to track in case I just want things to work
> locally)?

You can be excused for not checking the maintainer's private branches,
so just check the release branch.  If there's a patch in one the
maintainer may point it out to keep you informed, feel free to review
it to verify what is scheduled to be merged is complete.


More information about the Openembedded-core mailing list