On Tue, Jun 12, 2018 at 11:52 AM Andreas Grünbacher
> Quilt uses those Content-Disposition headers to preserve the patch
That' what I was assuming, but does anybody really care?
If you do things one patch at a time, maybe it's convenient, but then
it doesn't sound like a huge win either.
And if you do a patch-series, then it won't work anyway, and you'd be
saving to an mbox or something. Unless people save patch-series things
one by one, but at that point "convenient" is no longer an issue.
> Is this a new problem with gmail?
I don't know. I've seen it for a while, so it's not *new* new, but it
might be something like "the last few months". I know I saw it back in
March - and it was PeterZ then too. So it may literally be the case
that nobody else has sent me patches with quilt.
(Even if they use quilt to manage patches, maybe they don't _send_
them that way?)
How long has quilt been doing it?
Also, note that I'm not at all sure that it's _just_ the
that triggers this. There might be something else in those emails that
triggers it but that's the thing that stands out.
Attached is a png on how it looks on the gmail web interface (the
mobile version is similar - I don't use mobile for _work_, but I do
use it for keeping track of stuff that I want to know about, but don't
need to apply or do something about).
Notice how gmail tries to be helpful and make that "attachment" be
downloadable. It is indeed that. But it also makes it actually
illegible as an email.
> I'm not sure whose workflows would break if we kill those headers
> altogether, but maybe we can omit them by default.
That would be lovely at least for my case.
Quilt-dev mailing list