From: Peter Zijlstra <peterz@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Oleg Nesterov <oleg@redhat.com>,
Paul McKenney <paulmck@linux.vnet.ibm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Jean Delvare <jdelvare@suse.de>,
Andreas Gruenbacher <agruenba@redhat.com>
Subject: Quilt vs gmail (Was: [PATCH 0/3] sched/swait: Convert to full exclusive mode)
Date: Tue, 12 Jun 2018 19:14:20 +0200 [thread overview]
Message-ID: <20180612171420.GU12217@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CA+55aFzLNFO1za9-Lb=jxO_F9NS0jZyti+we=ycr5NTpgzdEbw@mail.gmail.com>
On Tue, Jun 12, 2018 at 09:47:34AM -0700, Linus Torvalds wrote:
> I do note how quilt emails are really hard to read, because that:
>
> Content-Disposition: inline
>
> makes gmail think it's flowed.
>
> Which works horribly badly for patches, surprise surprise.
>
> So I really wish quilt wouldn't do that. It does smell like a gmail
> bug, but at the same time, why would you use "Content-Disposition:
> inline" when you don't have an actual multi-part email? So I do blame
> quilt too for sending nonsensical headers.
>
> (Yes, yes, I see the "It is permissible to use Content-Disposition on
> the main body" in the RFC. But the RFC also makes it clear that it
> actually matters for how things are presented, so saying "ok, I'll do
> flowed" seems equally insane and equally technically RFC-compliant)
Quilt people, anything that can be done about that?
next prev parent reply other threads:[~2018-06-12 17:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 8:34 [PATCH 0/3] sched/swait: Convert to full exclusive mode Peter Zijlstra
2018-06-12 8:34 ` [PATCH 1/3] sched/swait: Remove __prepare_to_swait Peter Zijlstra
2018-06-20 9:39 ` [tip:sched/core] " tip-bot for Peter Zijlstra
2018-06-12 8:34 ` [PATCH 2/3] sched/swait: Switch to full exclusive mode Peter Zijlstra
2018-06-20 9:40 ` [tip:sched/core] " tip-bot for Peter Zijlstra
2018-06-12 8:34 ` [PATCH 3/3] sched/swait: Rename to exclusive Peter Zijlstra
2018-06-20 9:40 ` [tip:sched/core] " tip-bot for Peter Zijlstra
2018-06-12 16:47 ` [PATCH 0/3] sched/swait: Convert to full exclusive mode Linus Torvalds
2018-06-12 17:14 ` Peter Zijlstra [this message]
2018-06-13 12:32 ` Quilt vs gmail (Was: [PATCH 0/3] sched/swait: Convert to full exclusive mode) Jean Delvare
2018-06-13 13:27 ` Andreas Grünbacher
2018-06-13 13:48 ` Linus Torvalds
2018-06-13 14:40 ` Jean Delvare
2018-06-12 18:52 ` [PATCH 0/3] sched/swait: Convert to full exclusive mode Andreas Grünbacher
[not found] ` <CA+55aFx81igOjFZcvO03mvDFd3=pxsq2QuNrWrPW+4pvJy780A@mail.gmail.com>
2018-06-12 19:43 ` Thomas Gleixner
2018-06-12 21:54 ` Sebastian Andrzej Siewior
2018-06-12 22:03 ` Linus Torvalds
2018-06-12 22:55 ` Randy Dunlap
2018-06-13 13:00 ` [Quilt-dev] Quilt vs gmail Jean Delvare
2018-06-13 13:35 ` Greg KH
2018-06-14 1:27 ` [PATCH 0/3] sched/swait: Convert to full exclusive mode Paul E. McKenney
2018-06-19 14:49 ` Paul E. McKenney
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=20180612171420.GU12217@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=agruenba@redhat.com \
--cc=bigeasy@linutronix.de \
--cc=jdelvare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
--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