On March 9, 2018 00:35:06 Michel Dänzer <mic...@daenzer.net> wrote:
On 2018-03-08 07:53 PM, Jason Ekstrand wrote:
On Thu, Mar 8, 2018 at 8:45 AM, Dylan Baker <dy...@pnwbakers.com
<mailto:dy...@pnwbakers.com>> wrote:
> I know we've always given a lot of flexibility to vendor specific code
> (i965 or nouveau), but you hope everyone can understand my frustration
> with a 56 patch series that I sent review for 8 hours after it was
> posted to the list and I got told "Oh, I merged that hours ago,
> patches welcome."
I can. I guess Jason got a bit carried away by the Vulkan 1.1
excitement.
Perhaps. :-) I do think that being there day-1 is important.
The code was there on day 1 anyway. If being available in Git ASAP is
that important (not sure why though), it can be made available in a
repository other than the main shared one.
Thanks to things such as the oibaf ppa, landing in master means also
landing in the hands of users. There's a little extra delay but there are
piles of people who now have a Vulkan 1.1 driver who wouldn't build from
source. Maybe not a huge deal but landing in master does matter over
having a branch.
If nothing else, it shows the rest of the graphics community (who already
fears the concept of open-source) that working in the open isn't going
to cramp their style.
It wasn't following the normal Mesa development process, so I'm not sure
it's really useful for showing anything about that to anyone.
I'm not sure I follow.
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
