diff options
| -rw-r--r-- | Documentation/SubmittingPatches | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches index 1f4e8c8710a7..40b619ef9b6a 100644 --- a/Documentation/SubmittingPatches +++ b/Documentation/SubmittingPatches | |||
| @@ -725,7 +725,9 @@ maintainer pull them directly into the subsystem repository with a | |||
| 725 | "git pull" operation. Note, however, that pulling patches from a developer | 725 | "git pull" operation. Note, however, that pulling patches from a developer |
| 726 | requires a higher degree of trust than taking patches from a mailing list. | 726 | requires a higher degree of trust than taking patches from a mailing list. |
| 727 | As a result, many subsystem maintainers are reluctant to take pull | 727 | As a result, many subsystem maintainers are reluctant to take pull |
| 728 | requests, especially from new, unknown developers. | 728 | requests, especially from new, unknown developers. If in doubt you can use |
| 729 | the pull request as the cover letter for a normal posting of the patch | ||
| 730 | series, giving the maintainer the option of using either. | ||
| 729 | 731 | ||
| 730 | A pull request should have [GIT] or [PULL] in the subject line. The | 732 | A pull request should have [GIT] or [PULL] in the subject line. The |
| 731 | request itself should include the repository name and the branch of | 733 | request itself should include the repository name and the branch of |