4 ms·
The author mentions this several times, but the Linux kernel project workflow is built around email, as described on LWN[0] and discussed here[1] and on Reddit[
by jefurii 8y ago
The author mentions this several times, but the Linux kernel project workflow is built around email, as described on LWN[0] and discussed here[1] and on Reddit[2]. [edited for format]
[0] https://lwn.net/Articles/702177/ https://lwn.net/Articles/702177/
[1] https://news.ycombinator.com/item?id=15370620 https://news.ycombinator.com/item?id=15370620
[2] https://www.reddit.com/r/programming/comments/73gpys/why_linux_kernel_development_still_uses_email/ https://www.reddit.com/r/programming/comments/73gpys/why_lin...
- ChrisSD 8y agoAnd git was specifically designed for that workflow.
- wmf 8y agoYou have to do a bunch of squashing and rebasing to produce clean patch series; I wonder if there could be a better UX for that.
- pm215 8y agoI like 'stgit' for this -- it lets you manage a work-in-progress patch series as a stack of patches you can move around in, update, reorder and so on, which I find more natural than raw git rebases.
- ChrisSD 8y agoSince this is oddly getting down votes for some reason, I'll quote wikipedia[0]: > Git was created by Linus Torvalds in 2005 for development of the Linux kernel, with other kernel developers contributing to its initial development. [0] https://en.wikipedia.org/wiki/Git https://en.wikipedia.org/wiki/Git
- paulddraper 8y agoFurther, git provides utilities specifically meant to work with email workflows, e.g. git am.
- lsiebert 8y agogit itself uses the same process for patches.