From: Peter Zijlstra <peterz@infradead.org>
To: speck@linutronix.de
Subject: [MODERATED] Re: [patch 00/11] SSB v2
Date: Tue, 24 Apr 2018 19:02:48 +0200 [thread overview]
Message-ID: <20180424170248.GV4082@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <526897e6-dae9-a098-200a-e7253c6972a7@redhat.com>
On Mon, Apr 23, 2018 at 01:09:05PM -0400, speck for Jon Masters wrote:
> On 04/23/2018 12:25 PM, speck for Tim Chen wrote:
> > Please send me Thomas's tool and this patch series.
>
> Here's Thomas's tool, along with the workflow that Konrad suggested for
> how to plumb it together - it's what I used to send my update having at
> first not known about Thomas's scripts and gone down a path hacking my
> own (I strongly recommend everyone avoid GNU anubis btw...it's awful).
>
> A reminder that the scripts won't sanitize subjects. I got caught up
> with that one, so we should obfuscate those in the patch series (Konrad
> uses "Linux patch #1" etc..
I noticed that the patch series send to this list are not properly
threaded and suspect this script has something to do with it.
next prev parent reply other threads:[~2018-04-24 17:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 2:25 [MODERATED] [patch 00/11] SSB v2 konrad.wilk
2018-04-20 2:44 ` [MODERATED] " Konrad Rzeszutek Wilk
2018-04-20 2:53 ` Jon Masters
2018-04-20 3:15 ` Jon Masters
2018-04-20 6:00 ` Jon Masters
2018-04-22 10:01 ` Jon Masters
2018-04-22 10:10 ` Jon Masters
2018-04-23 16:25 ` Tim Chen
2018-04-23 16:30 ` Konrad Rzeszutek Wilk
2018-04-23 17:09 ` Jon Masters
2018-04-24 17:02 ` Peter Zijlstra [this message]
2018-04-24 18:00 ` Thomas Gleixner
2018-04-24 18:17 ` [MODERATED] " Jon Masters
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=20180424170248.GV4082@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=speck@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.