From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 0/3] [GIT PULL] tracing: Minor fixes for 5.1-rc2
Date: Tue, 26 Mar 2019 14:48:25 -0400 [thread overview]
Message-ID: <20190326144825.7b359641@gandalf.local.home> (raw)
In-Reply-To: <CAHk-=wiw+vH-LwFRv910FhojCHUDjwUJ4pNWVJkAiP=deyyG3Q@mail.gmail.com>
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
next prev parent reply other threads:[~2019-03-26 18:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 12:41 [PATCH 0/3] [GIT PULL] tracing: Minor fixes for 5.1-rc2 Steven Rostedt
2019-03-26 12:41 ` [PATCH 1/3] tracing: Remove unnecessary var_ref destroy in track_data_destroy() Steven Rostedt
2019-03-26 12:41 ` [PATCH 2/3] tracing: initialize variable in create_dyn_event() Steven Rostedt
2019-03-26 12:41 ` [PATCH 3/3] ftrace: Fix warning using plain integer as NULL & spelling corrections Steven Rostedt
2019-03-26 17:48 ` [PATCH 0/3] [GIT PULL] tracing: Minor fixes for 5.1-rc2 Linus Torvalds
2019-03-26 18:48 ` Steven Rostedt [this message]
2019-03-26 21:29 ` Linus Torvalds
2019-03-26 21:46 ` Steven Rostedt
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=20190326144825.7b359641@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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).