linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: asm-generic changes for 4.6
Date: Fri, 25 Mar 2016 16:17:01 +0100	[thread overview]
Message-ID: <4835715.nQCP8sPCa9@wuerfel> (raw)
In-Reply-To: <CA+55aFxd28NSi=Tka=JyYB57mu96DNzikydS3C_O98arPDDMvw@mail.gmail.com>

On Thursday 24 March 2016 23:29:31 Linus Torvalds wrote:
> On Thu, Mar 24, 2016 at 2:12 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> > asm-generic changes for 4.6
> 
> Btw, can you add "[GIT PULL]" to the subject line for your pulls? Or a
> "Please pull" in the body or similar.
> 
> When I do pulls, my email filter looks for (surprise surprise) the
> terms "git" and "pull".
> 
> And this didn't trigger either of those.
> 
> The normal git request-pull script has that "git" part, and some
> people just add the "Please pull" to the email, and my filter will
> pick that up too. But the easiest and preferred way for me to see pull
> requests ends up being that "[GIT PULL]" in the subject line. For the
> same reason I prefer "[PATCH x/y]" in the subject line for patches.
> 
> Not getting caught by my filter sometimes means that a pull gets
> delayed. Very seldom it might be overlooked entirely, but usually I do
> catch it later on after the other pulls (like happened now).
> 

Right. I realized my mistake the minute after sending the mail out,
but decided against sending it again immediately, assuming that you'd
either find it or I could resend the next day.

Thanks for pulling it in!

	Arnd

      reply	other threads:[~2016-03-25 15:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-24 21:12 asm-generic changes for 4.6 Arnd Bergmann
2016-03-25  6:29 ` Linus Torvalds
2016-03-25 15:17   ` Arnd Bergmann [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=4835715.nQCP8sPCa9@wuerfel \
    --to=arnd@arndb.de \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).