linux-kernel - Re: [PATCH 0/3] [GIT PULL] tracing: Minor fixes for 5.1-rc2

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:   Tue, 26 Mar 2019 14:48:25 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Linux List Kernel Mailing <linux-kernel@...r.kernel.org>,
        Ingo Molnar <mingo@...nel.org>,
        Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 0/3] [GIT PULL] tracing: Minor fixes for 5.1-rc2

On Tue, 26 Mar 2019 10:48:44 -0700
Linus Torvalds <torvalds@...ux-foundation.org> wrote:

> On Tue, Mar 26, 2019 at 5:42 AM Steven Rostedt <rostedt@...dmis.org> wrote:
> >
> > Please pull the latest trace-v5.1-rc2 tree, which can be found at:  
> 
> Pulled and pushed out, but for some reason the pr-tracker-bot doesn't
> seem to have reacted.
> 
> Presumably there's something in your git pull message that means it
> doesn't trigger.
> 
> And I suspect I know what it is: the patch that your subject line
> starts with "[PATCH..]" instead of "[GIT PULL..]"
>

Interesting. This is how I've always sent patches to you via quilt.

I usually don't put fixes sent to me through for-next, as I haven't
been convinced that that helps any. I make it a requirement to send any
patch I push into my tree for merging as a separate patch. As I usually
do that when I push to linux-next, if I send directly to you, I will
then send them individually.

The point being, when I send individual patches directly to you (and
not as a single email pull request), I use quilt sendmail. Which will
append the "[PATCH 0/x]" before my cover message subject.

Should I work on changing this?

-- Steve