Mesa's Lavapipe Vulkan Software Implementation Adds More Extensions

[phoronix]

Phoronix: Mesa's Lavapipe Vulkan Software Implementation Adds More Extensions

Mesa developer Mike Blumenkrantz who is employed by Valve and known for his work on the Zink OpenGL-on-Vulkan work has recently been working on enhancements to Lavapipe...

https://www.phoronix.com/scan.php?page=news_item&px=Lavapipe-March-2022-Extensions

[tildearrow]

cgit.freedesktop.org? Where's GitLab?

[oiaohm]

cgit.freedesktop.org? Where's GitLab?

Kind of example how simple it is to convert.
EXT_image_robustness

https://cgit.freedesktop.org/mesa/mesa/commit/?id=acb300a3f0284bd77c2433e89c5af31c2b998d8e

https://gitlab.freedesktop.org/mesa/mesa/-/commit/acb300a3f0284bd77c2433e89c5af31c2b998d8e

Notice that the id value can be just copy paste. I am not that sure that gitlab link here is a good idea tildearrow because cgit takes less network bandwidth than the gitlab interface to display the same thing. So least load on freedesktop servers using the cgit is the right answer.

The reality here cgit and gitlab have their advantages and it the reasons why freedesktop.org has kept on maintaining both options for accessing the repositories. Of course what you can see on the repository side with cgit is the same as what you can see on the gitlab side.

Do also note the cgit links did contain
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/15388> << bits that are links you have to copy paste back to the gitlab to get the discussion about the patches.

So everything is there just providing cgit links. So it now comes a chose of user friendliness vs hosting costs. cgit is slightly cheaper on hosting costs on bandwidth and cpu usage but is slightly less user-friendly and is missing a few features. Gitlab slightly more user-friendly but is also slightly more expensive on hosting costs in bandwidth and cpu usage.

tildearrow please beware I am not 100 percent sure what the right answer is here. With the amount of traffic a place like Phoronix can send to servers those slight differences in hosting costs could be critical. Personally think this cgit vs gitlab links is very much being caught between a rock and a hard place either way you choose you are wrong for different reasons and if you choose both you are absolutely even more wrong. So this might be case of no right answer. Pick one and hope to offend the least number of people.

[Quackdoc]

I prefer cgit for simple patches, and gitlab for more complicated ones, or PRs