From: Hans Schou <linux@schou.dk>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Andi Kleen <andi@firstfloor.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] SiS55x, another x86 CPU
Date: Thu, 16 Oct 2008 00:37:30 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0810160027150.7873@sko.w0.dk> (raw)
In-Reply-To: <Pine.LNX.4.64.0810152150070.25933@anakin>
On Wed, 15 Oct 2008, Geert Uytterhoeven wrote:
> On Wed, 15 Oct 2008, Andi Kleen wrote:
>>> If any CR/LF in your file you must have added them yourself.
>>
>> There were definitely CR/LFs in the patch attachment you sent.
>> And no my mailer doesn't add them.
>
> Interesting. I didn't see any CR/LFs neither, after exporting the
> attachment to a file (I'm using pine).
As far as I could see, Pine does this:
1. If file has not extension like: .zip .jpg .exe, see it as ASCII
2. Add CR/LF to the file
3. Encode file as base64
On reception of the file:
1. Decode file as specified (in this case base64)
2. If it looks like a text file, convert CR/LF to LF.
> However, when doing a base64 decode on the raw attachment data, the
> CR/LFs did pop up.
I think time is up for getting rid of Pine and there stupid license.
I'll check if "nail" can handle attachment correctly.
/hans
next prev parent reply other threads:[~2008-10-15 22:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-11 21:24 Hans Schou
2008-10-13 5:58 ` Andi Kleen
2008-10-13 20:56 ` Hans Schou
2008-10-14 6:06 ` Andi Kleen
2008-10-14 17:38 ` Hans Schou
2008-10-15 10:06 ` Andi Kleen
2008-10-15 19:51 ` Geert Uytterhoeven
2008-10-15 22:37 ` Hans Schou [this message]
2008-10-16 7:09 ` Geert Uytterhoeven
2008-10-16 19:01 ` Hans Schou
2008-10-16 19:18 ` Maciej W. Rozycki
2008-10-16 20:13 ` Hans Schou
2008-10-15 22:24 ` Hans Schou
[not found] ` <48F6E3DE.10206@zytor.com>
2008-10-16 18:47 ` Hans Schou
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0810160027150.7873@sko.w0.dk \
--to=linux@schou.dk \
--cc=andi@firstfloor.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®