Comment by cwillu

8 months ago

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.

4 comments

cwillu

Reply
micw  8 months ago

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.

  • cwillu  8 months ago

    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.

    • bmacho  8 months ago

      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?