@@ -209,7 +209,7 @@ send them as replies to either an additional "cover letter" message
209209(see below), the first patch, or the respective preceding patch.
210210
211211If your log message (including your name on the
212- Signed-off-by line ) is not writable in ASCII, make sure that
212+ ` Signed-off-by` trailer ) is not writable in ASCII, make sure that
213213you send off a message in the correct encoding.
214214
215215WARNING: Be wary of your MUAs word-wrap
@@ -229,7 +229,7 @@ previously sent.
229229The `git format-patch` command follows the best current practice to
230230format the body of an e-mail message. At the beginning of the
231231patch should come your commit message, ending with the
232- Signed-off-by: lines , and a line that consists of three dashes,
232+ ` Signed-off-by` trailers , and a line that consists of three dashes,
233233followed by the diffstat information and the patch itself. If
234234you are forwarding a patch from somebody else, optionally, at
235235the beginning of the e-mail message just before the commit
@@ -298,17 +298,14 @@ Do not forget to add trailers such as `Acked-by:`, `Reviewed-by:` and
298298patch.
299299
300300[[sign-off]]
301- === Certify your work by adding your " Signed-off-by: " line
301+ === Certify your work by adding your ` Signed-off-by` trailer
302302
303- To improve tracking of who did what, we've borrowed the
304- "sign-off" procedure from the Linux kernel project on patches
305- that are being emailed around. Although core Git is a lot
306- smaller project it is a good discipline to follow it .
303+ To improve tracking of who did what, we ask you to certify that you
304+ wrote the patch or have the right to pass it on under the same license
305+ as ours, by "signing off" your patch. Without sign-off, we cannot
306+ accept your patches .
307307
308- The sign-off is a simple line at the end of the explanation for
309- the patch, which certifies that you wrote it or otherwise have
310- the right to pass it on as an open-source patch. The rules are
311- pretty simple: if you can certify the below D-C-O:
308+ If you can certify the below D-C-O:
312309
313310[[dco]]
314311.Developer's Certificate of Origin 1.1
@@ -338,23 +335,29 @@ d. I understand and agree that this project and the contribution
338335 this project or the open source license(s) involved.
339336____
340337
341- then you just add a line saying
338+ you add a "Signed-off-by" trailer to your commit, that looks like
339+ this:
342340
343341....
344342 Signed-off-by: Random J Developer <random@developer.example.org>
345343....
346344
347- This line can be automatically added by Git if you run the git-commit
348- command with the -s option.
345+ This line can be added by Git if you run the git-commit command with
346+ the -s option.
349347
350- Notice that you can place your own Signed-off-by: line when
348+ Notice that you can place your own ` Signed-off-by` trailer when
351349forwarding somebody else's patch with the above rules for
352350D-C-O. Indeed you are encouraged to do so. Do not forget to
353351place an in-body "From: " line at the beginning to properly attribute
354352the change to its true author (see (2) above).
355353
354+ This procedure originally came from the Linux kernel project, so our
355+ rule is quite similar to theirs, but what exactly it means to sign-off
356+ your patch differs from project to project, so it may be different
357+ from that of the project you are accustomed to.
358+
356359[[real-name]]
357- Also notice that a real name is used in the Signed-off-by: line . Please
360+ Also notice that a real name is used in the ` Signed-off-by` trailer . Please
358361don't hide your real name.
359362
360363[[commit-trailers]]
0 commit comments