From: Linus Torvalds <torvalds@linux-foundation.org>
To: Mike Rapoport <rppt@kernel.org>
Cc: Alexander Gordeev <agordeev@linux.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Christian Brauner <brauner@kernel.org>,
David Hildenbrand <david@redhat.com>,
Gerald Schaefer <gerald.schaefer@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Matthew Wilcox <willy@infradead.org>,
Oleg Nesterov <oleg@redhat.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Wei Yang <richard.weiyang@gmail.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-s390@vger.kernel.org
Subject: Re: memblock: updates for 6.12-rc1
Date: Wed, 25 Sep 2024 11:50:10 -0700 [thread overview]
Message-ID: <CAHk-=wh=8JhAWjaxZPEOQgarTTsqPV0AQO=Q0USYtG009EYhUA@mail.gmail.com> (raw)
In-Reply-To: <20240923063707.40017-1-rppt@kernel.org>
On Sun, 22 Sept 2024 at 23:37, Mike Rapoport <rppt@kernel.org> wrote:
>
> memblock: updates for 6.12-rc1
Please make sure that there is a "git pull" somewhere in your pull request.
Now, the "git" part will always be there from a git request-pull (as
part of the "are available in the Git repository at" string), but I do
want to see a "pull" somewhere too. Otherwise my search functions
don't light up the email, and then it takes me longer to notice.
Most people put "[GIT PULL]" in the subject line, since that's also
how you get the attention of the pr-tracker-bot. So that's the
suggested way to do it, even if my search functionality is a lot more
permissive and just wants to see "git" and "pull" _somewhere_ in the
email.
You have done that in the past, I'm not sure why it didn't happen this time.
Linus
prev parent reply other threads:[~2024-09-25 18:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 6:37 Mike Rapoport
2024-09-25 18:50 ` Linus Torvalds [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHk-=wh=8JhAWjaxZPEOQgarTTsqPV0AQO=Q0USYtG009EYhUA@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=Liam.Howlett@oracle.com \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=david@redhat.com \
--cc=gerald.schaefer@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=richard.weiyang@gmail.com \
--cc=rppt@kernel.org \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox