From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757152AbYJPUNX (ORCPT ); Thu, 16 Oct 2008 16:13:23 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753681AbYJPUNK (ORCPT ); Thu, 16 Oct 2008 16:13:10 -0400 Received: from 0x55512ece.adsl.cybercity.dk ([85.81.46.206]:23302 "EHLO sko.w0.dk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753509AbYJPUNJ (ORCPT ); Thu, 16 Oct 2008 16:13:09 -0400 Date: Thu, 16 Oct 2008 22:13:06 +0200 (CEST) From: Hans Schou X-X-Sender: linux@sko.w0.dk To: "Maciej W. Rozycki" cc: Geert Uytterhoeven , linux-kernel@vger.kernel.org Subject: Re: [PATCH] SiS55x, another x86 CPU In-Reply-To: Message-ID: References: <87d4i5rq7i.fsf@basil.nowhere.org> <20081014060616.GO12131@one.firstfloor.org> <20081015100637.GS12131@one.firstfloor.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 16 Oct 2008, Maciej W. Rozycki wrote: > On Thu, 16 Oct 2008, Hans Schou wrote: > > > > But, why do you send patches as attachments in the first place? > > > > Ingo said I could do so when it was something to do with x86 patches. > > Anyway, it looks like ^R in Pine did work correctly. > > You've got: > > Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Thanks: [X] quell-flowed-text > in your headers -- it may be good for poetry, but will guarantee you > breakage with inline patches. There's an option to disable it. Maybe I should start on poetry instead of kernel-patching. "Tired of bugs? Then try Linux." ...I don't think I can do that for a living. /hans