mbox patch corruption?

Josh Boyer jwboyer at gmail.com
Tue Oct 7 00:02:32 EST 2008

On Sat, Oct 04, 2008 at 07:51:11AM +1000, Benjamin Herrenschmidt wrote:
>On Fri, 2008-10-03 at 08:51 -0400, Josh Boyer wrote:
>> On Fri, Oct 03, 2008 at 04:02:23PM +1000, Jeremy Kerr wrote:
>> >Hi Josh,
>> >
>> >> I've been doing some work with non-ascii encodings recently, so may
>> >> have broken this. Will take a look soon.
>> >
>> >Looks like this is a "technically correct, but useless" problem - the 
>> >email has a transfer encoding of quoted-printable, which is 
>> >encoding '<space><newline>' as '<space>=<newline><newline>'.
>> >
>> >However, most people aren't using the mbox files as actual mbox, so 
>> >perhaps an 8-bit raw encoding of utf-8 would be more appropriate.
>> I use them as an mbox all the time.  Basically, I collect up the
>> patches I want to put in my tree, download the mbox, and apply
>> them via 'git-am -i', wWhich expects an mbox.
>> The mbox file with those issues failed to apply via git, for
>> valid reasons since the patch was screwed up.
>Well, no, from what I understand, it's git who screws up if the
>mail is encoded in quoted printable no ? Anyway, no big deal, if
>patchwork can make sure the mbox is always encoded in UTF-8.

<parent hat>

I don't care who started it.  I just want it fixed!

</parent hat>



More information about the Patchwork mailing list