From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] You've got the "From " bug, I'm afraid.
Date: Sun, 09 Nov 2008 19:58:00 -0800 [thread overview]
Message-ID: <1226289411-sup-3516@entry> (raw)
In-Reply-To: <6bb609560811060321m61dc3f6by5cf603c406980628@mail.gmail.com>
Reformatted excerpts from barton.schaefer's message of 2008-11-06:
> Given the history, I think it's equally likely that RFC 4155 follows
> Pine. :-) The original mbox driver from the UW c-client package
> predates that RFC by nearly 20 years. 4155 is a case of documenting
> folklore so that newcomers don't have to learn it by hearsay.
Okee doke, I've made an official ditz issue to replicate this
20-year-old piece of work.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2008-11-10 3:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 3:41 Robin Lee Powell
2008-11-05 18:40 ` William Morgan
2008-11-05 20:00 ` Tomas Pospisek ML
2008-11-06 1:16 ` Bart Schaefer
2008-11-06 1:50 ` Tomas Pospisek ML
2008-11-06 11:21 ` Bart Schaefer
2008-11-10 3:58 ` William Morgan [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=1226289411-sup-3516@entry \
--to=wmorgan-sup@masanjin.net \
/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