Skip to content

Commit 8a356f5

Browse files
committed
btrfs-progs: README: reword DCO/Signed-off-by requirements
The Signed-off-by is not mandatory for changes to encourage contributions. As we'd still want to keep some quality level of final commits the patches may be updated. For that the Signed-off-by may be added even if there's no other such tag in the original contribution. [ci skip] Signed-off-by: David Sterba <[email protected]>
1 parent 864bdde commit 8a356f5

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

README.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -105,10 +105,11 @@ The development model of btrfs-progs shares a lot with the kernel model. The
105105
(typos, documentation) but is desired as this documents who authored the
106106
change, you can read more about the
107107
[The Developer's Certificate of Origin (chapter 11)](https://www.kernel.org/doc/html/latest/process/submitting-patches.html#sign-your-work-the-developer-s-certificate-of-origin)
108-
* if you are not used to the signed-off style, your contributions won't be
109-
rejected just because it's missing, the _Author:_ tag will be added as a
110-
substitute in order to allow contributions without much bothering with
111-
formalities
108+
* if you are not used to the signed-off-by style, your contributions won't be
109+
rejected just because it's missing, some other way of attribution will be
110+
used, like a link to issue or pull request to allow contributions without
111+
much bothering with formalities
112+
* project maintainers will add their Signed-off-by tag regardless
112113

113114
### Pull requests
114115

0 commit comments

Comments
 (0)