[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160727221546.GB14663@earth>
Date: Thu, 28 Jul 2016 00:15:47 +0200
From: Sebastian Reichel <sre@...nel.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: HSI changes for 4.8
Hi,
On Wed, Jul 27, 2016 at 12:15:18PM -0700, Linus Torvalds wrote:
> On Mon, Jul 25, 2016 at 1:52 PM, Sebastian Reichel <sre@...nel.org> wrote:
> > The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
> >
> > Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
> >
> > are available in the git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/sre/linux-hsi.git tags/hsi-for-4.8
>
> Btw, _please_ change your script to make sure the email has both "git"
> and "pull" in it somewhere. Without that, I don't see it with my
> normal search criteria for git pull requests, and during the merge
> window that often means that emails like that get overlooked.
>
> The preferred model tends to be to have "[GIT PULL]" at the beginning
> of the subject line, but even just a simple "please pull" in the body
> will trigger my search terms (together with the "git repository" thing
> from the boilerplate), so whatever is most convenient for you.
>
> This comes up pretty much every single merge window. People, please..
> I do try to notice pull requests and patches (for patches, please put
> "[PATCH x/y]" in the subject line) even when they don't trigger my
> usual search terms, but it really does help when emails match my
> simple rules.. I get too much email, making it easier for me to sort
> out pull requests really does make a difference.
Sorry, I currently write the pull request mails manually and forgot
to add it. I will prepare a script to avoid this in the future.
-- Sebastian
Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)
Powered by blists - more mailing lists