Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750904AbVL0PUP (ORCPT ); Tue, 27 Dec 2005 10:20:15 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751109AbVL0PUP (ORCPT ); Tue, 27 Dec 2005 10:20:15 -0500 Received: from mail.stdbev.com ([63.161.72.3]:28097 "EHLO mail.standardbeverage.com") by vger.kernel.org with ESMTP id S1750904AbVL0PUO (ORCPT ); Tue, 27 Dec 2005 10:20:14 -0500 Message-ID: Date: Tue, 27 Dec 2005 09:20:15 -0600 From: "Jason Munro" Subject: Re: recommended mail clients [was] [PATCH] ati-agp suspend/resume support (try 2) To: Jan Engelhardt Cc: , , , , Reply-to: In-Reply-To: References: <43AF7724.8090302@kroon.co.za> <43AFB005.50608@kroon.co.za> <1135607906.5774.23.camel@localhost.localdomain> <200512261535.09307.s0348365@sms.ed.ac.uk> X-Mailer: Hastymail 1.5-CVS x-priority: 3 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 Content-Length: 1648 Lines: 37 On 4:26:17 pm 26 Dec 2005 Jan Engelhardt wrote: > >> > >> I use pine and evolution. Pine is text based and great when I > >> ssh into my machine to work. Evolution is slow, but plays well > >> with pine and it handles things needed for LKML very well. (the > >> drop down menu "Normal" may be changed to "Preformat", which > >> allows of inserting text files "as-is"). > > > > Dare I say it, KMail has also been doing the Right Thing for a long > > time. It will only line wrap things that you insert by typing; > > pastes are left untouched. > > > > This satisfies Linus's demand that all patches be part of the email > > body and not an attachment. > > > Do not always blame the MUA, because actually, the MTAs may do > anything with the mail text. That's (among other reasons) why things > like MIME attachments were invented, because they (their respective > uuencoded or base64encoded "text") can be wrapped but does not change > the decoded form. - Something like that is in the pine doc. So which is preferable for someone handling inline patches. A properly encoded message text that when decoded with a compliant client accurately represents the original text (no whitespace mangling etc), or a message text that is accurate in it's raw state but may be altered during transit? \__ Jason Munro \__ jason@stdbev.com \__ http://hastymail.sourceforge.net/ - 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/