Identifying buggy patches with machine learning

Posted Nov 5, 2019 17:11 UTC (Tue) by zblaxell (subscriber, #26385)
In reply to: Identifying buggy patches with machine learning by zdzichu
Parent article: Identifying buggy patches with machine learning

$ git log --oneline v5.3..v5.3.8 | wc -l
1018

"mainline + 1018 patches + whatever cherries Fedora puts on top" is not, in any literal or practical sense, "mainline". It's not "production" either. At best, it's a late-stage CI artifact, an input to downstream integration and verification.

Identifying buggy patches with machine learning

Posted Nov 5, 2019 19:11 UTC (Tue) by zdzichu (subscriber, #17118) [Link]

I must have misunderstood. For me, everything coming from kernel.org is "mainline", but in this discussion this adjective seem to only be used to mean 5.x.0 releases, not even -stable releases.
In the opposition of "mainline" I see so called "distro" kernels with hundreds/thousands of patches and backports.