Code, conflict, and conduct
Code, conflict, and conduct
Posted Sep 21, 2018 17:34 UTC (Fri) by tbird20d (subscriber, #1901)In reply to: Code, conflict, and conduct by excors
Parent article: Code, conflict, and conduct
12. Please think about a single change that you made to the Linux kernel, that you did NOT submit upstream. Please answer the following questions to describe your reasons for NOT submitting your change:
...
15. My change was not good enough to submit to upstream (e.g. it was a quick hack or workaround, not suitable for upstream).
Strongly agree, agree, neutral, disagree, strongly disagree
16. I was afraid my patch would be rejected.
Strongly agree, agree, neutral, disagree, strongly disagree