From: William Allen Simpson <william.allen.simpson@gmail.com>
To: Valdis.Kletnieks@vt.edu
Cc: huananhu@huawei.com, David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 17/11]Optimize the upload speed for PPP connection.
Date: Tue, 17 Nov 2009 23:00:55 -0500 [thread overview]
Message-ID: <4B037177.7060501@gmail.com> (raw)
In-Reply-To: <13129.1258483787@turing-police.cc.vt.edu>
Valdis.Kletnieks@vt.edu wrote:
> The '-- ' *convention* isn't even at the next layer up, MIME. If anything,
> it's out at the liveware level (though some MUAs provide code to make it
> a bit easier to deal with...)
>
Hey Valdis, nice to hear from you....
> (Feel free to cite RFC chapter-and-verse if you disagree, and note that
> 'Informational' RFCs are never standards. ;)
>
Yeah, a quick check shows it's mentioned in MIME RFC-1341 (June 1992), but
certainly going back to "Proposed standard for message encapsulation"
RFC-934 (January 1985) at the very least. I seem to remember that Marshall
or Stef or somebody used it for digest sections too, but don't remember the
RFC number or a good search term.
Still, (relevance here) a convention observed for patches.
prev parent reply other threads:[~2009-11-18 4:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 9:19 [PATCH 17/11]Optimize the upload speed for PPP connection fangxiaozhi 00110321
2009-11-17 9:22 ` David Miller
2009-11-17 10:20 ` William Allen Simpson
2009-11-17 11:14 ` Jarek Poplawski
2009-11-17 11:49 ` William Allen Simpson
2009-11-17 11:54 ` Franko Fang
2009-11-17 11:49 ` David Miller
2009-11-18 5:04 ` William Allen Simpson
2009-11-18 7:51 ` Jarek Poplawski
2009-11-21 9:29 ` Pavel Machek
2009-11-21 12:21 ` Jarek Poplawski
2009-11-21 19:00 ` David Miller
2009-11-17 17:37 ` Alexander Clouter
2009-11-17 18:49 ` Valdis.Kletnieks
2009-11-18 4:00 ` William Allen Simpson [this message]
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=4B037177.7060501@gmail.com \
--to=william.allen.simpson@gmail.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=davem@davemloft.net \
--cc=huananhu@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.