linux-kernel - Re: asm-generic changes for 4.6

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 24 Mar 2016 23:29:31 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	"linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: asm-generic changes for 4.6

On Thu, Mar 24, 2016 at 2:12 PM, Arnd Bergmann <arnd@...db.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).

                Linus