diff options
| author | Jonathan Corbet <corbet@lwn.net> | 2014-12-23 09:28:40 -0700 |
|---|---|---|
| committer | Jonathan Corbet <corbet@lwn.net> | 2014-12-23 09:28:40 -0700 |
| commit | b792ffe464f64c84c48d51e01c0fecabc4b39579 (patch) | |
| tree | cd3aa55ad59289c85648b4f969bbb827a25714a6 | |
| parent | 082bd1ca9a7eaf28695d8bab9adcff54f77c040c (diff) | |
Docs: SubmittingPatches: mention using pull requests as a cover letter
Suggested-by: Mark Brown <broonie@kernel.org>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
| -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 "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 |