I started trying out the plaintext email workflow recently. One thing is very clear - all that pain is only because of bad tools and nothing to do with workflow

I started trying out the plaintext email workflow recently. One thing is very clear - all that pain is only because of bad tools and nothing to do with workflow itself. Regular email clients (incl webclients) garble the workflow horribly - HTML by default, top posting with no easy way to correct it, and attachment handling that assumes the user to be an idiot. I use neomutt. It's hard to learn and it's not the best an email client can be. But it makes git-email workflow and mailing list handling much more pleasant. There is more that can be done. Better GUI and web clients for plain text email can help. Clients can display issue threads better. Patch mails can be combined. There can be an interface to import the patches easily. There can be optional markdown/ReST/asciidoc rendering. Similar improvements can be made with mailing lists too. With good tools, email workflow can be more pleasant and more intuitive than Fork-PR.