Managing Patch Submissions with b4
b4 is a tool that handles the fiddly parts of email-based development: fetching someone else's series from the archives so you can test it, preparing and sending your own, and collecting the review tags people reply with. It removes most of the reasons a first-time contributor's email arrives malformed. It also makes reviewing other people's work easy, which is the fastest way to learn. Doing all of it by hand is possible and error-prone.
Questions this Concept answers
- Why does using `b4` remove most of the reasons a first-time contributor's patch email arrives malformed?
am,shazam: retrieving and applying patches
Kernel development happens over email, and b4 is the tool that handles the awkward parts of that workflow. Given the message id of a patch series someone posted, it fetches the whole thread from the …