From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 11 May 2001 18:51:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 11 May 2001 18:51:08 -0400 Received: from intranet.resilience.com ([209.245.157.33]:54239 "EHLO intranet.resilience.com") by vger.kernel.org with ESMTP id ; Fri, 11 May 2001 18:50:59 -0400 Mime-Version: 1.0 Message-Id: In-Reply-To: <20010511133242.B3224@bacchus.dhis.org> In-Reply-To: <80BTbI6mw-B@khms.westfalen.de> <20010511133242.B3224@bacchus.dhis.org> Date: Fri, 11 May 2001 15:49:05 -0700 To: Ralf Baechle From: Jonathan Lundell Subject: Re: [PATCH] adding PCI bus information to SCSI layer Cc: Kai Henningsen , linux-kernel@vger.kernel.org Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org At 1:32 PM -0300 2001-05-11, Ralf Baechle wrote: >On Thu, May 03, 2001 at 12:51:25AM -0700, Jonathan Lundell wrote: >> Kai Henningsen wrote: >> >What's a lot more important is that the mail standards say that this stuff >> >should not be interpreted by the receivers as needing wrapping, so >> >irregardless of good or bad design it's just plain illegal. >> > >> >If you want to support wrapping with plain text, investigate >> >format=flowed. >> >> Yes, I did that. >> > > I'm curious, though: I haven't found the mail standards that forbid >> receivers to wrap long lines. Certainly many mail clients do it. >> What's the relevant RFC? > >RFC 2822, 2.1.1. Thanks. It's not quite a standard yet, but it's true, it does limit lines to 998 characters. Sort of a strange limit, but there you are.... -- /Jonathan Lundell.