Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 15 Jan 2002 18:15:00 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 15 Jan 2002 18:14:08 -0500 Received: from fungus.teststation.com ([212.32.186.211]:62980 "EHLO fungus.teststation.com") by vger.kernel.org with ESMTP id ; Tue, 15 Jan 2002 18:14:03 -0500 Date: Wed, 16 Jan 2002 00:13:48 +0100 (CET) From: Urban Widmark X-X-Sender: To: Patrick Mochel cc: Nicolas Pitre , Subject: Re: Why not "attach" patches? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 15 Jan 2002, Patrick Mochel wrote: > It doesn't at all. It silently removes extra white space at the end of > lines. It's been a "feature" since about 4.30 or so. I am pretty sure that it works fine in RedHat's 4.33 version (or else Linus would have dropped some of my patches ... er, more of my patches :). But I haven't checked how that version differs from the original. At the end is a simple ^R-ed file that works for me sending to myself. But I don't think it is related to ^R ... (should be 3 spaces after that line) If you postpone a message it has a silly idea to add an empty line at the end. But that shouldn't break patches. /Urban no space tab 3 spaces no space - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/