diff options
| author | Matthew Wilcox | 2018-04-06 14:02:35 -0700 |
|---|---|---|
| committer | Jonathan Corbet | 2018-04-16 14:42:58 -0600 |
| commit | 3b443955596e8f9965dbf11bd9bc0554c8b63781 (patch) | |
| tree | fdf5d5125ba73b1cc71b5242fa3cbea70730afc0 /Documentation/process | |
| parent | 6d9094862b70020c684588147e5eff52dec19c8d (diff) | |
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>
Diffstat (limited to 'Documentation/process')
| -rw-r--r-- | Documentation/process/submitting-patches.rst | 2 |
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:: |