Re:The X.Org Server just got forked (announcing XLibre)
by cwillu on Friday June 06, 2025 @07:57AM
(#44199938)
Wow: “xrandr doesn't work anymore on xorg-git” “I do not think this should be specifically on you, it is not unreasonable to expect that the author of a change tries their change before even submitting it upstream.” does not give a warm fuzzy feeling about the author of the at-fault patch leading a fork.
[ Parent
| on HN ]
Re:The X.Org Server just got forked (announcing XLibre)
by DarkmSparks on Friday June 06, 2025 @08:33AM
(#44200208)
It happens. No one writes bug free code.
e.g.
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests...
Re:The X.Org Server just got forked (announcing XLibre)
by micw on Friday June 06, 2025 @03:56PM
(#44204395)
I think it's not the one to blame who broke this but those who implemented everything all the time without adding any tests. Xorg has quite a large codebase but almost no automated tests.
Re:The X.Org Server just got forked (announcing XLibre)
by cwillu on Friday June 06, 2025 @06:33PM
(#44205683)
So we agree that the maintainer is at fault: he wanted to change things and not have to thoroughly test his changes by doing the boring work of adding test coverage to the modified area.
Re:The X.Org Server just got forked (announcing XLibre)
by bmacho on Sunday June 15, 2025 @07:31AM
(#44281772)
There is no arguing about that, the maintainer made a mistake. (Among other people, and it was insignificant anyway.)
So now that we agree on this, what now? How exactly does
> does not give a warm fuzzy feeling about the author of the at-fault patch leading a fork.
follow? E.g. do you think that none of the Wayland developers ever made any mistakes?