The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Mary Ann Horton <mah@mhorton.net>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] fmt(1): history, POSIX, -t, -c
Date: Thu, 28 May 2020 14:00:41 -0400	[thread overview]
Message-ID: <CAC20D2ORERmQM02cG=D2YWShwg_jJq5avHrYHV6Lz5VZ7JUsig@mail.gmail.com> (raw)
In-Reply-To: <fa5e315c-5719-dd7e-4564-67726b1a9651@mhorton.net>

[-- Attachment #1: Type: text/plain, Size: 1264 bytes --]

On Thu, May 28, 2020 at 12:10 PM Mary Ann Horton <mah@mhorton.net> wrote:

> It's nice to see a uuencode email attachment once again!
>
I was worried a MIME attachment might not get passed through the
automation, so I stayed with tried and true methods.

> Clem (who, by the way, is correct about the origin of fmt, it was part of
> Kurt Shoens' Mail program at Berkeley) has perfect timing. This coming
> Monday, 6/1/2020, is the 40th anniversary of the uuencode email attachment.
> (The date is based on the date in the uuencode man page in the 2.8BSD and
> 4.2BSD archives at https://www.tuhs.org/Archive/Distributions/UCB/ )
>
I could not have told you date, but I do remember when you sent it ber and
myself, specifically.

There has been some amusing coverage of the "25th anniversary of the email
attachment", commemorating Nat Borenstien's creation of MIME in 1992.
And his scheme does not work on IBM Mainframes or 6-bit machine as is (Nat
required an 8 bit path).  Your scheme passed through all known systems at
the time.

> Any thoughts on a proper commemoration of the 40th anniversary?
>
Can't say I know the proper way to do that, other than to say thank you and
acknowledge the hack as a darned creative solution to an issue a lot of us
had.

Clem

[-- Attachment #2: Type: text/html, Size: 2798 bytes --]

  reply	other threads:[~2020-05-28 18:01 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-28 12:34 markus schnalke
2020-05-28 13:08 ` Rob Pike
2020-05-28 13:30 ` Clem Cole
2020-05-28 13:47   ` Clem Cole
2020-05-28 16:08     ` Mary Ann Horton
2020-05-28 18:00       ` Clem Cole [this message]
2020-05-28 18:35         ` Richard Salz
2020-05-28 18:51           ` Clem Cole
2020-05-29  0:18   ` Greg 'groggy' Lehey
2020-05-29  5:10     ` Michael Stiller via TUHS
2020-05-29  5:19       ` Greg 'groggy' Lehey
2020-05-29 13:39       ` Clem Cole
2020-05-29 15:43         ` Warner Losh
2020-05-29 16:12           ` Clem Cole
2020-05-29 17:14         ` Mary Ann Horton
2020-05-28 13:46 ` Clem Cole
2020-05-31 13:01   ` [TUHS] mh/hm, mmh (was: fmt(1): history, POSIX, -t, -c) markus schnalke
2020-05-31 14:53     ` Clem Cole
2020-05-31 16:25       ` Richard Salz
2020-05-31 16:50         ` Larry McVoy
2020-05-31 17:09       ` Ralph Corderoy
2020-05-31 17:25         ` Jon Steinhart
2020-05-31 17:28       ` [TUHS] mh/hm, mmh Mary Ann Horton
2020-05-31 18:56         ` Eric Allman
2020-05-31 19:49           ` Clem Cole
2020-05-31 21:31           ` Mary Ann Horton
2020-06-01  6:32             ` Caipenghui
2020-06-01  7:14             ` markus schnalke
2020-05-31 12:35 ` [TUHS] fmt(1): history, POSIX, -t, -c markus schnalke
2020-05-29  1:25 Doug McIlroy

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='CAC20D2ORERmQM02cG=D2YWShwg_jJq5avHrYHV6Lz5VZ7JUsig@mail.gmail.com' \
    --to=clemc@ccc.com \
    --cc=mah@mhorton.net \
    --cc=tuhs@minnie.tuhs.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;
as well as URLs for NNTP newsgroup(s).