IMHO the pain already kicks in since discourse isn’t a proper mailing
list. It mangles with all the inputs.
→ missing attachment, not really actionable. Copying a patch from the
modified mail output is also not fun.
→ the pastebin that was used to circument discourse shortcomings
expired
→ has been handled by ryantm
→ more corrupt patches due to discourse
Of course we can now try to repair all those issues and still call it
not painful. At least in my case those patches also arrived via email
but were converted into some markdown gibberish. Not very helpful.
Patch submission to our project should just work like everywhere else
(where mail is supported): git-send-email shouldn’t be rejected as
invalid and should not be mangled by the ML software (discourse in our
case).