On Fri, Apr 06, 2018 at 11:32:11AM -0700, Linus Torvalds wrote: > On Fri, Apr 6, 2018 at 11:21 AM, Linus Torvalds > <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote: > > > > No, but if you can redo the pull request part so that the diffstat I > > get will match the diffstat I see in the pull request, that would be > > good. > > Oh, and can you please make sure there is a "[GIT PULL]" in the > subject line for your pull requests? > > Particularly during the merge window (not so much later) I end up > having a separate filtered list of emails that I look at that mention > "git pull". > > Your pull requests don't seem to match that, so your pull requests > don't actually even show up in my list of pending pull requests. We have out of date information in Documentation ... Jon, please consider applying: 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:: -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
