2 ms·
All this tool is doing is making Github a fancy web frontend for sending a patch to the LKML. From that perspective, all this does is make it more convenient fo
by vlovich123 5y ago
All this tool is doing is making Github a fancy web frontend for sending a patch to the LKML. From that perspective, all this does is make it more convenient for those with a GitHub account to not have to learn a totally new workflow. I would think this would be easily portable to any other service (e.g. create a similar bot for Gitlab, Bitbucket, etc).
There's a separate discussion about whether the workflow more broadly should move out of the LKML. This might look like having patch sets posted to the LKML automatically ingested into Gerrit.
All of this seems pretty sane to modernize the workflow & make it a more familiar one for those working on the Linux kernel professionally. E-mailing patch sets around is decidedly a very old way to do code review that's not generally found in modern professional shops (cries of "this is for the worse" notwithstanding because that feels like a VIM vs emacs complaint).