From: Steven Willoughby <stevew@nffs.com>
To: stevew@nffs.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] adding PCI bus information to SCSI layer
Date: 11 May 2001 17:00:34 -0600 [thread overview]
Message-ID: <989622044.448.1.camel@STEVE> (raw)
In-Reply-To: <p0510030db7221c090810@[10.128.7.49]>
In-Reply-To: <p05100303b70eadd613b0@[207.213.214.37]> <80BTbI6mw-B@khms.westfalen.de> <p0510030ab716bdcf5556@[207.213.214.37]> <20010511133242.B3224@bacchus.dhis.org> <p0510030db7221c090810@[10.128.7.49]>
> >>
> > > 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....
>
Perhaps it's 998 so that with the \r\n end of line it rounds out to an
even 1000.
That limit is slightly more sensical.
Steven
next prev parent reply other threads:[~2001-05-11 23:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2001-05-11 22:49 ` Jonathan Lundell
2001-05-12 2:20 ` Ralf Baechle
2001-05-12 4:21 ` Jonathan Lundell
[not found] <p0510030db7221c090810@[10.128.7.49]=FE2>
2001-05-12 11:00 ` Kai Henningsen
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=989622044.448.1.camel@STEVE \
--to=stevew@nffs.com \
--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®