On Thu, Sep 15, 2016 at 5:54 AM, Austin S. Hemmelgarn <ahferro...@gmail.com> wrote: > > > I specifically do not think we should worry about distro kernels though.
It will be essentially impossible to keep such a thing up to date. It's difficult in the best case scenario to even track upstream's own backports to longterm kernels, whether those would actually even change anything in the matrix. I'd say each major version gets it's own page, and just dup the page for each version. So for starters, the current page is for version 4.7. If when 4.8 is released there's no significant change in stability that affects the color (stability status) of any listed feature, then that page could say 4.7 through current. If it's true that the status page has no major changes going back to 4.4 through current, label it that way. As soon as there's a change that affects the color coding of an item in the grid, duplicate the page. Old page gets a fixed range of kernels, say 4.4 to 4.7. And now the newest page is 4.8 - current. I think a column for version will lose the historical perspective of when something goes from red to yellow, yellow to green. > If > someone is using a specific distro, that distro's documentation should cover > what they support and what works and what doesn't. Some (like Arch and to a > lesser extent Gentoo) use almost upstream kernels, so there's very little > point in tracking them. Some (like Ubuntu and Debian) use almost upstream > LTS kernels, so there's little point tracking them either. Many others > though (like CentOS, RHEL, and OEL) Use forked kernels that have so many > back-ported patches that it's impossible to track up-date to up-date what > the hell they've got. A rather ridiculous expression regarding herding of > cats comes to mind with respect to the last group. Yeah you need the secret decoder ring to sort it out. Forget it, not worth it. -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html