Comparing and Contrasting Patman Vs B4 for Posting Patches
summary
Compares PatMan and B4 for posting Linux patches, showing concrete behavior: PatMan (a 12‑year‑old U‑Boot tool with Linux support since 2013) embeds metadata in commits, strips Gerrit change‑id, parallelizes checkpatch, and calls get_maintainer per patch but still requires SMTP; B4 (kernel.org tool) stores metadata in an empty metadata commit, integrates tightly with lore, can send without SMTP via lore, auto‑increments revisions, fetches reviewed/tested tags and supports cryptographic patch attestation. Choice hinges on whether per‑patch version history or lore integration matters.
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
38mCode Review vs Pul Requests
43mBeginner Linux kernel maintainers toolbox
34mContributing your first patch to the Qt Project
46mLinux Kernel Development for Newbies
41mhkml: Mailing Tool for Simple Linux Kernel Development
25mHow the magic of open source helps our project
32mHow big of a problem are Un-upstreamed patches