b4

Later in the thread it seems like https://github.com/mricon/b4 was involved. Maybe just a bug this time but exposes it as a weak link in the whole kernel contributor web of trust

I recently switched to neomutt and offlineimap/isync as my email client. I tried really hard after that to get a setup going so that I could accept git patches mailing list wise. I had to figure out how to set up a keyboard macro with just the right incantation[1] of b4[2]. I realized accepting patches meant my friends would also have to learn (neo)mutt if I wanted them to accept mine. It was really difficult. I can't imagine asking my friends to do that and collaborating with them. (I still like mutt though and still use it as my main client.) By the way, good luck getting that set up to work on Windows, which a large population of developers use because of their work laptops (or because they simply prefer the interface!). I made a script[3] that makes it easy to accept patches using an fzf interface, as a sort of reply to git-send-email

> But in some ways it isn’t. Like any fool (like me) can just get some Emacs configuration for free from others. To be clear though: there are programs and tools beyond the git(1) tools themselves that help you with email workflows. Like b4 which is for the Linux workflow. https://github.com/mricon/b4