From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757420AbYJPTSV (ORCPT ); Thu, 16 Oct 2008 15:18:21 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756468AbYJPTSL (ORCPT ); Thu, 16 Oct 2008 15:18:11 -0400 Received: from ftp.linux-mips.org ([213.58.128.207]:48898 "EHLO ftp.linux-mips.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756361AbYJPTSK (ORCPT ); Thu, 16 Oct 2008 15:18:10 -0400 Date: Thu, 16 Oct 2008 20:18:04 +0100 (BST) From: "Maciej W. Rozycki" To: Hans Schou 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> User-Agent: Alpine 1.10 (LFD 962 2008-03-14) 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, 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 in your headers -- it may be good for poetry, but will guarantee you breakage with inline patches. There's an option to disable it. Maciej