[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANK3SE3V9CwNL=xydkvjuTtnktJyHM7g3s6MSiLRQcS7ppqncQ@mail.gmail.com>
Date: Tue, 30 Aug 2011 11:31:30 +0100
From: Mark Einon <mark.einon@...il.com>
To: Alan Cox <alan@...rguk.ukuu.org.uk>
Cc: Dan Carpenter <error27@...il.com>, gregkh@...e.de,
devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
o.hartmann@...ovital.com
Subject: Re: [PATCH 4/6] staging: et131x: Remove redundant replica loopback code
On 30 August 2011 11:17, Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
> On Tue, 30 Aug 2011 13:08:34 +0300
> Dan Carpenter <error27@...il.com> wrote:
>
>> This patch was sent with git-send-email but it's in base64 encoding.
>>
>> Content-Type: text/plain; charset="utf-8"
>> Content-Transfer-Encoding: base64
>>
>> Why did that happen?
>
> Presumably it got re-encoded because a mail system in the path between
> him and you decided it was traversing a 7bit path and helpfully
> reprocessed it to avoid corruption.
>
> If your mailer can't automatically handle utf-8/base64 perhaps you need a
> better one ;)
Maybe not - now you mention it, when git send-email got to this
particular patch, it did ask me if I wanted to use UTF-8, which it's
never done before.
I'm not aware of anything unusual I did with this patch set, but i've
just done a format-patch and git send-email again to get:
git send-email --to=mark.einon@...il.com
0004-staging-et131x-Remove-redundant-replica-loopback-cod.patch
0004-staging-et131x-Remove-redundant-replica-loopback-cod.patch
The following files are 8bit, but do not declare a Content-Transfer-Encoding.
0004-staging-et131x-Remove-redundant-replica-loopback-cod.patch
Which 8bit encoding should I declare [UTF-8]?
Not sure how that's happened.
Mark
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists