mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kaih@khms.westfalen.de (Kai Henningsen)
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] adding PCI bus information to SCSI layer
Date: 12 May 2001 13:00:00 +0200	[thread overview]
Message-ID: <80knzI9mw-B@khms.westfalen.de> (raw)
In-Reply-To: =?ISO-8859-1?Q?<p0510030db7221c090810@[10.128.7.49]=FE2>?=

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 1175 bytes --]

jlundell@pobox.com (Jonathan Lundell)  wrote on 11.05.01 in <p0510030db7221c090810@[10.128.7.49]·2>:

> 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....

It's the unchanged old RFC 821 SMTP line length limit [4.5.3 SIZES, text  
line] (the consequences are just spelt out more clearly). And 821 is from  
1982, so this is certainly not new in any sense of the word.

MfG Kai

       reply	other threads:[~2001-05-12 11:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <p0510030db7221c090810@[10.128.7.49]=FE2>
2001-05-12 11:00 ` Kai Henningsen [this message]
2001-04-24 21:02 Matt_Domsch
2001-04-24 21:59 ` Richard Gooch
2001-04-27  4:31   ` Richard Gooch
2001-05-01  1:27     ` Richard Gooch
2001-05-01  8:46       ` Ingo Oeser
2001-05-01 16:53       ` Richard Gooch
2001-05-01 20:32         ` Alan Cox
2001-05-02 15:03           ` Ingo Oeser
2001-05-02 15:54             ` Alan Cox
2001-05-03  8:57           ` Chris Wedgwood
2001-05-03  9:49             ` Alan Cox
2001-05-03 10:23               ` Chris Wedgwood
2001-04-24 23:16 ` Jonathan Lundell
2001-04-27  5:24   ` Jonathan Lundell
2001-05-01 14:38     ` Jonathan Lundell
2001-05-03  7:32     ` Kai Henningsen
2001-05-03  7:51     ` Jonathan Lundell
2001-05-11 16:32       ` Ralf Baechle
2001-05-11 23:00         ` Steven Willoughby
2001-05-11 22:49       ` Jonathan Lundell
2001-05-12  2:20         ` Ralf Baechle
2001-05-12  4:21         ` Jonathan Lundell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=80knzI9mw-B@khms.westfalen.de \
    --to=kaih@khms.westfalen.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®