lkml.org 
[lkml]   [2019]   [Mar]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH 0/3] [GIT PULL] tracing: Minor fixes for 5.1-rc2
    On Tue, 26 Mar 2019 10:48:44 -0700
    Linus Torvalds <torvalds@linux-foundation.org> wrote:

    > On Tue, Mar 26, 2019 at 5:42 AM Steven Rostedt <rostedt@goodmis.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

    \
     
     \ /
      Last update: 2019-03-26 19:48    [W:2.175 / U:0.224 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site