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.
@123e16e8 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).