'signed-off-by' is a linux kernel convention; by adding your Signed-off-by line to a patch, you are certifying that you have read and understood the Developer Certificate of Origin (DCO), originated in 2004 by the Linux foundation as an affirmation that the source code being submitted originated from the developer, or that the developer has permission to submit the code. Many projects follow the same conventions used by the linux kernel.
https://en.wikipedia.org/wiki/Developer_Certificate_of_Origin
On Thu, Oct 17, 2019 at 4:31 AM Uwe Kleine-König uwe@kleine-koenig.org wrote:
On 10/17/19 10:51 AM, Gerd Hoffmann wrote:
On Thu, Oct 17, 2019 at 09:44:38AM +0200, Uwe Kleine-König wrote:
I'm still unclear about that Signed-of-by concern.
Re-send patches with Signed-of-by added to the commit message. Git can do that automatically for you (-s switch for "git commit"). It's used to keep track of the patch workflow (who wrote the patch, who reviewed & committed, ...).
I would have expected that the "who wrote" is obvious from the Author: line in the commit, "who reviewed" by something like "Reviewed-by:" and the committer from the Committer line.
For the projects I usually interact with Signed-off-by has a juristic meaning, see my mail from Monday.
If the Signed-off-by here really only has the purpose to show through which hands the patch went in, I can resend of course.
Best regards Uwe
SeaBIOS mailing list -- seabios@seabios.org To unsubscribe send an email to seabios-leave@seabios.org