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

[Kubo Da Costa, Raphael]

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)?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3298 bytes
Desc: not available
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20181116/51ff3ca7/attachment-0001.bin>