summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMatthew Wilcox <willy@infradead.org>2018-04-07 00:02:35 +0300
committerJonathan Corbet <corbet@lwn.net>2018-04-16 23:42:58 +0300
commit3b443955596e8f9965dbf11bd9bc0554c8b63781 (patch)
treefdf5d5125ba73b1cc71b5242fa3cbea70730afc0
parent6d9094862b70020c684588147e5eff52dec19c8d (diff)
downloadlinux-3b443955596e8f9965dbf11bd9bc0554c8b63781.tar.xz
Docs: tell maintainers to put [GIT PULL] in their subject lines
It seems that Linus looks for [GIT PULL] in subject lines to ensure that pull requests don't get buried in the noise during merge windows. Update the docs to reflect that. [jc: From an impromptu post from willy, thus no SOB] Signed-off-by: Jonathan Corbet <corbet@lwn.net>
-rw-r--r--Documentation/process/submitting-patches.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst
index f7152ed565e5..908bb55be407 100644
--- a/Documentation/process/submitting-patches.rst
+++ b/Documentation/process/submitting-patches.rst
@@ -761,7 +761,7 @@ 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
+A pull request should have [GIT PULL] in the subject line. The
request itself should include the repository name and the branch of
interest on a single line; it should look something like::