diff options
Diffstat (limited to 'Documentation/SubmittingPatches')
-rw-r--r-- | Documentation/SubmittingPatches | 25 |
1 files changed, 8 insertions, 17 deletions
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches index 9838d32b2fe7..4d1f41b84ebc 100644 --- a/Documentation/SubmittingPatches +++ b/Documentation/SubmittingPatches | |||
@@ -132,21 +132,6 @@ which require discussion or do not have a clear advantage should | |||
132 | usually be sent first to linux-kernel. Only after the patch is | 132 | usually be sent first to linux-kernel. Only after the patch is |
133 | discussed should the patch then be submitted to Linus. | 133 | discussed should the patch then be submitted to Linus. |
134 | 134 | ||
135 | For small patches you may want to CC the Trivial Patch Monkey | ||
136 | trivial@rustcorp.com.au set up by Rusty Russell; which collects "trivial" | ||
137 | patches. Trivial patches must qualify for one of the following rules: | ||
138 | Spelling fixes in documentation | ||
139 | Spelling fixes which could break grep(1). | ||
140 | Warning fixes (cluttering with useless warnings is bad) | ||
141 | Compilation fixes (only if they are actually correct) | ||
142 | Runtime fixes (only if they actually fix things) | ||
143 | Removing use of deprecated functions/macros (eg. check_region). | ||
144 | Contact detail and documentation fixes | ||
145 | Non-portable code replaced by portable code (even in arch-specific, | ||
146 | since people copy, as long as it's trivial) | ||
147 | Any fix by the author/maintainer of the file. (ie. patch monkey | ||
148 | in re-transmission mode) | ||
149 | |||
150 | 135 | ||
151 | 136 | ||
152 | 5) Select your CC (e-mail carbon copy) list. | 137 | 5) Select your CC (e-mail carbon copy) list. |
@@ -271,7 +256,7 @@ patch, which certifies that you wrote it or otherwise have the right to | |||
271 | pass it on as a open-source patch. The rules are pretty simple: if you | 256 | pass it on as a open-source patch. The rules are pretty simple: if you |
272 | can certify the below: | 257 | can certify the below: |
273 | 258 | ||
274 | Developer's Certificate of Origin 1.0 | 259 | Developer's Certificate of Origin 1.1 |
275 | 260 | ||
276 | By making a contribution to this project, I certify that: | 261 | By making a contribution to this project, I certify that: |
277 | 262 | ||
@@ -291,9 +276,15 @@ can certify the below: | |||
291 | person who certified (a), (b) or (c) and I have not modified | 276 | person who certified (a), (b) or (c) and I have not modified |
292 | it. | 277 | it. |
293 | 278 | ||
279 | (d) I understand and agree that this project and the contribution | ||
280 | are public and that a record of the contribution (including all | ||
281 | personal information I submit with it, including my sign-off) is | ||
282 | maintained indefinitely and may be redistributed consistent with | ||
283 | this project or the open source license(s) involved. | ||
284 | |||
294 | then you just add a line saying | 285 | then you just add a line saying |
295 | 286 | ||
296 | Signed-off-by: Random J Developer <random@developer.org> | 287 | Signed-off-by: Random J Developer <random@developer.example.org> |
297 | 288 | ||
298 | Some people also put extra tags at the end. They'll just be ignored for | 289 | Some people also put extra tags at the end. They'll just be ignored for |
299 | now, but you can do this to mark internal company procedures or just | 290 | now, but you can do this to mark internal company procedures or just |