diff options
Diffstat (limited to 'Documentation/SubmittingPatches')
| -rw-r--r-- | Documentation/SubmittingPatches | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches index 72651f788f4e..689e2371095c 100644 --- a/Documentation/SubmittingPatches +++ b/Documentation/SubmittingPatches | |||
| @@ -98,6 +98,17 @@ system, git, as a "commit log". See #15, below. | |||
| 98 | If your description starts to get long, that's a sign that you probably | 98 | If your description starts to get long, that's a sign that you probably |
| 99 | need to split up your patch. See #3, next. | 99 | need to split up your patch. See #3, next. |
| 100 | 100 | ||
| 101 | When you submit or resubmit a patch or patch series, include the | ||
| 102 | complete patch description and justification for it. Don't just | ||
| 103 | say that this is version N of the patch (series). Don't expect the | ||
| 104 | patch merger to refer back to earlier patch versions or referenced | ||
| 105 | URLs to find the patch description and put that into the patch. | ||
| 106 | I.e., the patch (series) and its description should be self-contained. | ||
| 107 | This benefits both the patch merger(s) and reviewers. Some reviewers | ||
| 108 | probably didn't even receive earlier versions of the patch. | ||
| 109 | |||
| 110 | If the patch fixes a logged bug entry, refer to that bug entry by | ||
| 111 | number and URL. | ||
| 101 | 112 | ||
| 102 | 113 | ||
| 103 | 3) Separate your changes. | 114 | 3) Separate your changes. |