Re: [OE-core][dunfell 00/12] Pull request (cover letter only)

["Richard Purdie" <richard.purdie@linuxfoundation.org>]

On Thu, 2020-10-15 at 04:20 -1000, Steve Sakoman wrote:
> On Thu, Oct 15, 2020 at 4:13 AM Joshua Watt <jpewhacker@gmail.com>
> wrote:
> > On Thu, Oct 15, 2020 at 9:07 AM Steve Sakoman <steve@sakoman.com>
> > wrote:
> > > Gentle reminder :-)
> > > 
> > > On Tue, Oct 13, 2020 at 5:14 PM Steve Sakoman via
> > > lists.openembedded.org <steve=sakoman.com@lists.openembedded.org>
> > > wrote:
> > > > The following changes since commit
> > > > 552739383321bd9b4780bd0026d6107ece530522:
> > > > 
> > > >   perl: fix ptest test count (2020-10-05 04:29:40 -1000)
> > > > 
> > > > are available in the Git repository at:
> > > > 
> > > >   git://git.openembedded.org/openembedded-core-contrib
> > > > stable/dunfell-next
> > > >   
> > > > http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/dunfell-next
> > > > 
> > > > Bruce Ashfield (4):
> > > >   linux-yocto/5.4: fix kprobes build warning
> > > >   linux-yocto/5.4: update to v5.4.67
> > > >   linux-yocto/5.4: update to v5.4.68
> > > >   linux-yocto/5.4: update to v5.4.69
> > > > 
> > > > Joshua Watt (1):
> > > >   classes/sanity: Bump minimum python version to 3.5
> > 
> > I assume since this passed on the AB, that 3.5 is actually the
> > minimum
> > tested version of dunfell, and changing on a stable branch won't be
> > a
> > problem?
> > 
> > Do we know if anyone is using OE core with 3.4? It seems unlikely
> > since bitbake has a minimum version of 3.5.
> 
> The fact that bitbake has a minimum version of 3.5 is what convinced
> me to include this patch, it seemed silly to have a mismatch between
> oe-core and bitbake.

Its effectively a no-op but does clean up the confusion about what out
minimum version is which is why I was happy enough to see it go to
dunfell.

I had merged Steve's series but not run "push", sorry :)

Cheers,

Richard