zlacker

[parent] [thread] 4 comments
1. cwillu+(OP)[view] [source] 2025-06-06 11:57:51
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.
replies(2): >>DarkmS+m4 >>micw+T91
2. DarkmS+m4[view] [source] 2025-06-06 12:33:28
>>cwillu+(OP)
It happens. No one writes bug free code.

e.g.

https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests...

3. micw+T91[view] [source] 2025-06-06 19:56:05
>>cwillu+(OP)
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.
replies(1): >>cwillu+Fu1
◧◩
4. cwillu+Fu1[view] [source] [discussion] 2025-06-06 22:33:26
>>micw+T91
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.
replies(1): >>bmacho+Uhl
◧◩◪
5. bmacho+Uhl[view] [source] [discussion] 2025-06-15 11:31:56
>>cwillu+Fu1
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?
[go to top]