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 17:46:23 -0400 [thread overview]
Message-ID: <20190326174623.16d7725f@gandalf.local.home> (raw)
In-Reply-To: <CAHk-=wg5_Hu4W5tz05vmC3eBH3_h7_uJKEMwLM+MvsJ=znWtbw@mail.gmail.com>
On Tue, 26 Mar 2019 14:29:27 -0700
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Tue, Mar 26, 2019 at 11:48 AM Steven Rostedt <rostedt@goodmis.org> wrote:
> >
> > Should I work on changing this?
>
> I don't personally much care, but the pr-tracker-bot clearly does.
>
> If you don't care about the automated "it's been pulled" message, that
> doesn't matter, of course.
I'm subscribed to your git tree and filter out all updates for my
signed off by. An then I get those emails. So I get the "Pulled"
message regardless.
>
> That said, I'd almost prefer to get just the regular pull request
> without the patches. If the complete patch is small, it's often nice
> to see that _in_ the pull request (at the bottom), but I don't
> generally need or want the individual patches themselves as separate
> emails (unless there's some particular reason you want me to comment
> on something, or apply them directly as patches).
It's not really for you, but more for transparency in general. I have a
rule that I don't push anything to you that I haven't personally sent
to LKML as a separate patch.
It's not a big deal. I could make this a two step process, and send
these as my "for-next" patches so that people (including the authors of
the patch) know that I'm sending them upstream.
-- Steve
prev parent reply other threads:[~2019-03-26 21:46 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
2019-03-26 21:29 ` Linus Torvalds
2019-03-26 21:46 ` Steven Rostedt [this message]
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=20190326174623.16d7725f@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).