On Fri, Apr 03, 2020 at 11:40:28PM +0000, George Spelvin wrote: > I understand that it's addressed more to patch authors than > maintainers forwarding them, but I've read that thing a dozen times, > and the description of S-o-b always seemed to be about copyright. >
It's to say that you didn't add anything which you shouldn't have, for example, secret SCO UnixWare stuff. > So I had assumed that edits which were below the de minimus standard > of copyright didn't need a separate S-o-b. > > Am I right that there should be an S-o-b from everyone from the > patch author to the patch committer (as recorded in git)? And the > one exception is that we don't need S-o-b for git pulls after that, > because the merge commits record the information? Yes. Also if people added their S-o-b for git merges it would change the git hash for the patch which would suck. regards, dan carpenter _______________________________________________ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
