 There are a lot of benefits in mailing list based development, but there are so many ways to do something wrong: send a patch to a wrong message/thread, forget cover letter or In-Reply-To header, attach instead of inline and so on. Technically all the tools are available, but it takes a tangible amount of time and practice to configure them and start doing everything properly. Resources like https://git-send-email.io/ helps, but still doesn't solve the issue completely. 7 comments
@fosskers That's right. > So Codeberg or...? IDK to be honest. I really like the offline friendlines of emails and it's a huge deal for me right now. Overall, I'm good with sourcehut, but sometimes I have troubles with poorly formed patch series without cover letters or sent to a separate thread instead of reroll to the same one.  @abcdw I like the patch-over-mailing-list approach as a submitter. I do occasionally mess things up, but usually the reviewers will pardon me for sending a v2. As for git send-email, I donโt like it much. The "mail user agent" function of git send-email is very unpleasant, because you canโt review what you did, it does not copy the email in your sent folder, you canโt apply filters. While claiming to be the only working MUA (the one you use daily being unworthy of that name). @gugurumbe for editing capabilities it's possible to add --compose switch and/or combine git send-email with format-patches, but yes, overall you aright, it's not very friendly MUA experience. Totally agree. I ended up writing a script for submitting the patch series. And still it is cumbersome. |
Gregory's Server
@abcdw i hate it tbh. much prefer gerrit or phabricator plus a chat channel