|
|
|
|
|
by GW150914
2816 days ago
|
|
It would cost you nothing to replace your last line with, “I’m sorry, but that’s not what we’re seeing and we won’t merge it until you fix it. I understand your passion, but I won’t sacrifice the quality of this project for that. Fix the code so that it no longer invokes undefined behavior and we’ll review it, otherwise we have nothing more to talk about.” The end. No need to call it crap, no need to burn a bridge. |
|
Personally, I just stop responding after the technical arguments have been exchanged. There is no point in repeating what was ignored already, no point in ELI5, no point to using swear words, silence is what works best.
By the way, if you told me "I understand your passion, but...", I'd be angry beyond belief. That's the way you talk to children, and even my mother is no longer allowed to talk to me like that. I consider that a stronger insult than my code being called crap. Which probably shows that shutting up in time is the best response.