3 ms·
>A person randomly shows up to report and attempt fix a bug in an "obscure"(?) architecture Everyone involved in this story, both the original author, the seco
by Arnavion 3y ago
>A person randomly shows up to report and attempt fix a bug in an "obscure"(?) architecture
Everyone involved in this story, both the original author, the second person who authored the patch, and the maintainer who reviewed it, are on the mailing list for that obscure architecture. It's obvious that they all care about it. Its "obscurity" in your eyes is irrelevant.
>In this case, from a utilitarian perspective, it doesn't seem obvious the maintainer should spend the extra time coaching.
https://news.ycombinator.com/item?id=37675328 https://news.ycombinator.com/item?id=37675328
- hnfong 3y ago> https://news.ycombinator.com/item?id=37675328 https://news.ycombinator.com/item?id=37675328 I was replying to a specific comment suggesting that the maintainer should do a code review, give comments and ask for an update to the patch, instead of rewriting the patch. Quoting my words out of context isn't helpful here.
- Arnavion 3y agoAnd my point was that from "a utilitarian perspective" there's a middle ground between "coach the original author to produce a better patch" and "commit your own patch without crediting the original author"; it's "commit your own patch while crediting the original author". There's no "out of context" quoting in my comment.