Moving code around, post classic

2021-12-06 Thread Dylan Baker
Classic is gone, and the cleanups have begun, obviously. There is another cleanup that I had in mind, which is moving src/mesa into src/gallium/frontends/mesa. This makes the build system a little cleaner, as currently we do some bending over backwards to get gallium, mesa, and their tests built

Amber branch plan

2021-12-06 Thread Dylan Baker
Since classic is gone, I thought I'd lay out my thinking for Amber. I'm assuming that we'll branch Amber from the 21.3 branch, after that reaches normal EOL. That gives us the benefit of developing on top of a known good state for classic drivers, and should minimize friction for distros dealing

Re: Amber branch plan

2021-12-06 Thread Jason Ekstrand
+1 On Mon, Dec 6, 2021 at 5:51 PM Dylan Baker wrote: > Since classic is gone, I thought I'd lay out my thinking for Amber. > > I'm assuming that we'll branch Amber from the 21.3 branch, after that > reaches normal EOL. That gives us the benefit of developing on top of a > known good state for

Re: Moving code around, post classic

2021-12-06 Thread Marek Olšák
Hi, 1. If this happens, let's call it src/gallium/frontends/gl. 3. The src directory already has too much stuff. Marek On Mon, Dec 6, 2021 at 6:51 PM Dylan Baker wrote: > Classic is gone, and the cleanups have begun, obviously. There is > another cleanup that I had in mind, which is moving

Re: Moving code around, post classic

2021-12-06 Thread Jason Ekstrand
On Mon, Dec 6, 2021 at 5:50 PM Dylan Baker wrote: > Classic is gone, and the cleanups have begun, obviously. There is > another cleanup that I had in mind, which is moving src/mesa into > src/gallium/frontends/mesa. This makes the build system a little > cleaner, as currently we do some bending