Skip to content

Commit bd49690

Browse files
Commit signoff requirement clarification (#172)
Expanded description about signing off commits.
2 parents 2584141 + 9e4dede commit bd49690

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

doc/_dev-guide/chapter_5/section_7.md

+1
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,7 @@ guidelines the following:
2020
for syslog-ng. Please try to follow the existing conventions.
2121
4. Always add a `Signed-off-by` tag to the end of **every** commit
2222
message you submit.
23+
Signing off on commits enables users to affirm that a commit complies with the rules and licensing of a repository. This, in the case of {{ site.product.short_name }}, means that you accept our coding and contribution standards described in the Contribution section, and accept that your code will be published with a `GPLv2` license.
2324
5. Always create a separate branch for the pull request, forked off
2425
from the appropriate {{ site.product.short_name }} branch.
2526
6. If your patch should be applied to multiple branches, submit

0 commit comments

Comments
 (0)