From: Joe Perches <joe@perches.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Petr Mladek <pmladek@suse.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [GIT PULL] tracing: Fix to recursion protection for 5.15
Date: Wed, 20 Oct 2021 23:36:47 -0700 [thread overview]
Message-ID: <14e76713c9d7dec2ce368a983c67bbffd8691551.camel@perches.com> (raw)
In-Reply-To: <CAHk-=wicuM=0iMeRCrbG=MMLZRdwihpZ64rWxDqidEjMa-YDsA@mail.gmail.com>
On Wed, 2021-10-20 at 20:27 -1000, Linus Torvalds wrote:
> On Wed, Oct 20, 2021 at 8:16 PM Joe Perches <joe@perches.com> wrote:
> >
> > Generally, a tool like b4 should be able to create a list of any
> > email addresses in a thread linked commit.
>
> I really think Cc lines are very useful.
>
> That said, they are *more* useful when they are thought about, than
> when they are automated.
[]
> I will, for example, strive to put the people who _participated_ in
> some discussion as the "Cc" list - they may not have acked a patch, or
> reviewed it, but they might have piped up in the discussion, and that
> probably merits them then knowing about any problems it causes.
Which is exactly what "thread linked commit" attempted to convey.
next prev parent reply other threads:[~2021-10-21 6:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 13:13 Steven Rostedt
2021-10-20 16:10 ` Linus Torvalds
2021-10-20 16:17 ` Steven Rostedt
2021-10-20 20:59 ` Linus Torvalds
2021-10-20 22:12 ` Steven Rostedt
2021-10-20 22:41 ` Steven Rostedt
2021-10-21 6:08 ` Linus Torvalds
2021-10-21 6:16 ` Joe Perches
2021-10-21 6:27 ` Linus Torvalds
2021-10-21 6:36 ` Joe Perches [this message]
2021-10-20 16:16 ` pr-tracker-bot
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=14e76713c9d7dec2ce368a983c67bbffd8691551.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®