LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Hans Schou <linux@schou.dk>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] SiS55x, another x86 CPU
Date: Tue, 14 Oct 2008 19:38:52 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0810140828220.11184@sko.w0.dk> (raw)
In-Reply-To: <20081014060616.GO12131@one.firstfloor.org>

On Tue, 14 Oct 2008, Andi Kleen wrote:

>>> Your attachment seems to be windows line end damaged.
>>
>> Strange, Pine usually do it right with file attachments.
>
> It likely was added on some Windows system.

>> (what is "windows line end damaged"?)
>
> It used MSDOS style \r\n line terminators instead of Unix style \n.

Yes, I do know what a CR/LF (Carriage Return Line Feed) is but I 
didn't send any. I really dont understand what you are talking about.

I looked at the mail returned from vger.kernel.org which was fine, and 
this web-page is also OK.
http://www.gossamer-threads.com/lists/linux/kernel/983150

There is no CR here:
od -t x1 patch-sis55x | grep 0d

If any CR/LF in your file you must have added them yourself.

/hans

  reply	other threads:[~2008-10-14 17:39 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 [this message]
2008-10-15 10:06         ` Andi Kleen
2008-10-15 19:51           ` Geert Uytterhoeven
2008-10-15 22:37             ` Hans Schou
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.0810140828220.11184@sko.w0.dk \
    --to=linux@schou.dk \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [PATCH] SiS55x, another x86 CPU' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).