[PATCH] skip original Content-Transfer-Encoding for mbox

In the commit 01b9cbb9 all original mail headers are copied into the resulted mbox file. This means that some headers are going to be present twice in the generated mbox. That is fine unless the original email arrived in base64 encoding. Apparently git relies on the latest

Re: [PATCH v2 0/2] Patchwork 2.1.0-rc1: Eolienne

> Personally I'd rather wait on the two things you mentioned below. The > API changes in particular are extensive enough and I'd like people > testing these as soon as possible (e.g. RC1). After that though, I'm > good: things like the labels feature can definitely wait a while > longer. > >> * I

Re: [PATCH] skip original Content-Transfer-Encoding for mbox

- Original Message - > From: "Daniel Axtens" > To: patchwork@lists.ozlabs.org, vkaba...@redhat.com, "yuri volchkov" > > Sent: Monday, May 7, 2018 5:57:55 PM > Subject: [PATCH] skip original Content-Transfer-Encoding for mbox > > In the commit