Comparing and Contrasting Patman Vs B4 for Posting Patches
summary
PatMan automates git format-patch/send-email, enforces per-commit tags for fine-grained version history, calls checkpatch in parallel, calls get_maintainer per patch and automatically strips Change-Id but still requires an SMTP server. B4 centralizes metadata in an empty commit, integrates tightly with lore to fetch prior versions and tags, can submit via kernel.org web endpoint without SMTP, auto-increments revisions and provides patch attestation and Lore integration for message links.
AI-written summary · about
chapters (9)
- 0:00Patch posting tools intro
- 4:56PatMan overview
- 13:29Why use PatMan
- 27:54PatMan features
- 28:17B4 introduction
- 33:33B4 no SMTP
- 35:59B4 metadata
- 45:02PatMan vs B4
- 47:05Final thoughts & Q&A
related talks
49mComparing and Contrasting Patman Vs B4 for Posting Patches
37mGetting Your Patches in Mainline Linux: What Not To Do (& a Few Things You Could Try
38mCode Review vs Pul Requests
49mMaking your patch more committable
58mHow To Get Your Patch Accepted
32mHow (Not) to Get the Vendor Driver Merged Upstream
53mUpstreaming 201
21mSyzbot To Mainline: How I Merged 21 Kernel Patches as a First-Time Contributor