Em Fri, 11 Oct 2019 11:32:54 -0700 (PDT) David Miller <da...@davemloft.net> escreveu:
> From: Steven Rostedt <rost...@goodmis.org> > Date: Fri, 11 Oct 2019 14:01:08 -0400 > > > Thus, if we want people to send us their fixes, we better keep just > > an email with a patch the lowest bar for entry. > > I argue that for people coming into the software engineering world > today, a PR is the lowest bar for entry. And email is the exact > opposite, _especially_ our way of doing email. > > Because it IS NOT just an email with a patch. > > It is an email with a specific Subject line format, with various > fields. Some field are optional and some are mandatory, and it also > depends upon which tree you are targetting. > > Then there is the commit message which has content and formatting > requirements. > > And then there are the tags, of various types and flavors, and the > context (which is sometimes subtle) determines which of those tags are > relevant and how they should be filled in. > > The various other standard email fields like TO: and CC: have to > be set a certain way otherwise the patch won't even be looked at. I can't see how just adding a web interface like github/gitlab would solve any of the above. I mean, the submitter will still need to write a proper subject/description before submitting the patch to the web interface, add the tags, etc. The only thing that would be different if we write a a Kernel-specific web GUI would be to automate some sanity checks on it, like starting a CI build for the patch series, run checkpatch and get_maintainers, but that could also happen if we write a script/submit_patches tool, that would internally call checkpatch, get_maintainers and git send e-mail (or use some other interface like patchwork REST to submit patches). Thanks, Mauro _______________________________________________ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
