4 ms·
It's about maintaining a clean codebase. If a maintainer believes that a proposal is genuinely the wrong way to achieve a goal, it is counterproductive to acce
by tux1968 13y ago
It's about maintaining a clean codebase. If a maintainer believes that a proposal is genuinely the wrong way to achieve a goal, it is counterproductive to accept it. This happens all the time in the Linux kernel for instance, where one or more further iterations are required to get something accepted. It's just juvenile to stamp ones feet because some upstream disagrees with a particular approach. You argue the technical merits, and then you live with their decision by going your own way or revamping your submission. It's hard to imagine open source working any other way.
- AsymetricCom 13y agoI thought it was more about making it impossible to use GPUs to guide cruise missiles, but that might be a bit presumptuous.
- joe_the_user 13y agoSo you're saying Wilson thought Mir would allow a clean code base a few days ago when he accepted a Mir patch and now he doesn't, despite not giving any technical reasons for the change in opinion? (Me - complete outside but the turn of events sure sounds fishy).