Message ID | 418d15c53268f947e11dac2f22d1f8c3c8c60997.1603155607.git.bkuhn@sfconservancy.org (mailing list archive) |
---|---|
State | Accepted |
Commit | 53147b0d3bc0994104726ec790a4bcb7da68544e |
Headers | show |
Series | clarify meaning of --signoff & related doc improvements in describing Signed-off-by | expand |
Junio, Junio wrote in the sub-thread about [PATCH v3 4/4]: >> It seems the patches [1-3/4] are identical to what has been queued >> in 'seen', which is a good sign. One change I made in v3 patchset was to add Peff's Signed-off-by, as it is *not* there in commit 04c2b9ebd0 in seen: I wrote in [PATCH v3 2/4]: > Signed-off-by: Jeff King <peff@peff.net> … given that Peff made edits to this before it was posted, I think we want to be sure Peff's Signed-off-by is included. It just seems like the "right thing" to get the Signed-off-by trailers 100% correct on a commit that changes the description of Signed-off-by.
On Tue, Oct 20, 2020 at 02:44:31PM -0700, Bradley M. Kuhn wrote: > > Reviewed-by: Taylor Blau <me@ttaylorr.com> > > I doubt Taylor cares whether this Reviewed-by trailer makes it in, > but I did add that too based on Taylor providing it earlier in the > discussion of this patch. ☺ He doesn't ;-). Thanks, Taylor
diff --git a/Documentation/signoff-option.txt b/Documentation/signoff-option.txt index d1c6713774..fbff8dd5be 100644 --- a/Documentation/signoff-option.txt +++ b/Documentation/signoff-option.txt @@ -3,12 +3,16 @@ ifdef::git-commit[] endif::git-commit[] --signoff:: --no-signoff:: - Add Signed-off-by line by the committer at the end of the commit - log message. The meaning of a signoff depends on the project, - but it typically certifies that committer has - the rights to submit this work under the same license and - agrees to a Developer Certificate of Origin - (see http://developercertificate.org/ for more information). + Add a Signed-off-by trailer by the committer at the end of the commit + log message. The meaning of a signoff depends on the project + to which you're committing. For example, it may certify that + the committer has the rights to submit the work under the + project's license or agrees to some contributor representation, + such as a Developer Certificate of Origin. + (See http://developercertificate.org for the one used by the + Linux kernel and Git projects.) Consult the documentation or + leadership of the project to which you're contributing to + understand how the signoffs are used in that project. + The --no-signoff option can be used to countermand an earlier --signoff option on the command line.