On 08/29/2017 10:34 AM, Ben Hutchings wrote: > On Tue, 2017-08-29 at 09:53 -0600, Jens Axboe wrote: >> On 08/29/2017 09:48 AM, Jens Axboe wrote: >>> On 08/29/2017 09:28 AM, Ben Hutchings wrote: >>>> On Tue, 2017-08-29 at 08:31 -0600, Jens Axboe wrote: >>>>> On Sun, Aug 13 2017, Ben Hutchings wrote: >>>>>> The block core requests modules with the "-iosched" name >>>>>> suffix, but >>>>>> bfq no longer has that suffix. Add an alias. >>>>> >>>>> I'd apply these two, but both patches are mangled when saved. >>>>> It's >>>>> turning == into =3D and so forth. >>>>> >>>>> Care to check your settings and resend? >>>> >>>> Just tried saving and applying with 'git am' successfully. I >>>> think the >>>> problem is at your end. >>> >>> Then yours is the only one, I apply patches people send me all day >>> long. >>> Was the case both in tbird and mutt, both of them showed the diffs >>> as mangled, and they showed up mangled when saved. >> >> Here's your email in the archive: >> >> https://marc.info/?l=linux-block&m=150264374920778&q=raw >> >> Note this part: >> >> Content-Transfer-Encoding: quoted-printable > > What about it? This is used for every mail with a non-ASCII name in > it, for example. 'git am' understands it. What about it? It screws up the patch. Maybe git am understands it, but it's hard/impossible to read manually. I'm not going to apply anything that I can't personally read/review easily. Fix your setup, if you are going to be sending patches. >> Problem is definitely at your end. > > Or perhaps in the middle? Anyway, here are the patches again as an > mbox. Feel free to browse other patches on the list, I don't see any that are quoted-printable. And I'd know, since I generally end up applying (or at least reviewing) most of them. -- Jens Axboe
