Quilt vs gmail (Was: [PATCH 0/3] sched/swait: Convert to full exclusive mode)
- Date: Tue, 12 Jun 2018 19:14:20 +0200
- From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
- Subject: Quilt vs gmail (Was: [PATCH 0/3] sched/swait: Convert to full exclusive mode)
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?