From: Jonathan Corbet Date: Tue, 23 Dec 2014 16:28:40 +0000 (-0700) Subject: Docs: SubmittingPatches: mention using pull requests as a cover letter X-Git-Tag: firefly_0821_release~176^2~2358^2~6^2 X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=b792ffe464f64c84c48d51e01c0fecabc4b39579;p=firefly-linux-kernel-4.4.55.git Docs: SubmittingPatches: mention using pull requests as a cover letter Suggested-by: Mark Brown Signed-off-by: Jonathan Corbet --- 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 "git pull" operation. Note, however, that pulling patches from a developer requires a higher degree of trust than taking patches from a mailing list. As a result, many subsystem maintainers are reluctant to take pull -requests, especially from new, unknown developers. +requests, especially from new, unknown developers. If in doubt you can use +the pull request as the cover letter for a normal posting of the patch +series, giving the maintainer the option of using either. A pull request should have [GIT] or [PULL] in the subject line. The request itself should include the repository name and the branch of