[Mesa-dev] [RFC] Concrete proposal to split classic

[Alyssa Rosenzweig]

> Probably nv30 would do well to "move on" as well. But it also presents
> an interesting question -- the nv30 driver has lots of problems. I
> have no plans to fix them, nor am I aware of anyone else with such
> plans. However if such a developer were to turn up, would it be
> reasonable to assume that their work would ultimately land in this
> "lts" branch/tree/whatever? Some of the "fixes" will require large-ish
> changes to the driver...

AFAIU, the issue isn't large changes to the driver, but large changes to
common code. So unless you're switching it to NIR or something, it
probably doesn't matter.