From 434c76ca91e9def899355914473a03441697b896 Mon Sep 17 00:00:00 2001 From: kpande Date: Wed, 31 May 2017 10:30:07 -0400 Subject: [PATCH] Explain reason for Signed-off-by in CONTRIBUTING Reviewed-by: Giuseppe Di Natale Reviewed-by: Brian Behlendorf Reviewed-by: George Melikov Reviewed-by: Haakan T Johansson Signed-off-by: Kash Pande Closes #6183 --- .github/CONTRIBUTING.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index 3f0b4eadd9..46923b5ee0 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -165,8 +165,12 @@ first line in the commit message. please summarize important information such as why the proposed approach was chosen or a brief description of the bug you are resolving. Each line of the body must be 72 characters or less. -* The last line must be a `Signed-off-by:` line with the developer's -name followed by their email. +* The last line must be a `Signed-off-by:` tag with the developer's +name followed by their email. This is the developer's certification +that they have the right to submit the patch for inclusion into +the code base and indicates agreement to the [Developer's Certificate +of Origin](https://www.kernel.org/doc/html/latest/process/submitting-patches.html#sign-your-work-the-developer-s-certificate-of-origin). +Code without a proper signoff cannot be merged. Git can append the `Signed-off-by` line to your commit messages. Simply provide the `-s` or `--signoff` option when performing a `git commit`.