From: Michael Usher via TUHS <tuhs@minnie.tuhs.org>
To: Jacob Goense <dugo@xs4all.nl>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] [COFF] Topics...
Date: Tue, 7 Jul 2020 16:45:57 -0700 [thread overview]
Message-ID: <CACg3+DG8sfarqWZM5N3Yijc0dH6LzVtYJtMG+PYTV=Dem6+2tQ@mail.gmail.com> (raw)
In-Reply-To: <97902a98ce76c281160840d78ed838be@xs4all.nl>
[-- Attachment #1: Type: text/plain, Size: 1117 bytes --]
I usually edit it to say "Was (not Was)".
Hmmm. Wouldn't it be great if we had a Markov chain subject generator that
sourced the actual email thread contents as its driver, and then when the
topic drifted far enough, it simply replaced the subject line with a new
creation ?
Ooohhh -- another idea -- RFC5322 states that subject may occur from 0 to 1
times per email. Why don't we just delete the subject lines entirely?
Michael
(it's late. I need to poke a bear)
On Tue, Jul 7, 2020 at 4:30 PM Jacob Goense <dugo@xs4all.nl> wrote:
> On 2020-07-08 00:53, Dave Horsfall wrote:
> > On one list I use, a predecessor of it used to require a subject tag
> > in the form [Blah] (taken from a set of known tags); I've always hated
> > that, but I'm still in the habit of putting my own tag there as a
> > hint.
>
> When I have tuned out of a long running thread and the topic drifts
> significantly I'm always grateful to the kind soul that tags..:
>
> Subject: Re: new [was: old]
>
--
Michael Usher
Senior Wireless Network Engineer
University of California, Santa Cruz
musher@ucsc.edu 831-459-3697
[-- Attachment #2: Type: text/html, Size: 1850 bytes --]
next prev parent reply other threads:[~2020-07-07 23:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 2:11 [TUHS] Topics Grant Taylor via TUHS
2020-07-07 2:56 ` [TUHS] [COFF] Topics Adam Thornton
2020-07-07 14:33 ` [TUHS] Topics Tomasz Rola
2020-07-07 14:38 ` Alan D. Salewski
2020-07-07 15:26 ` John Cowan
2020-07-07 22:53 ` [TUHS] [COFF] Topics Dave Horsfall
2020-07-07 23:23 ` Jacob Goense
2020-07-07 23:45 ` Michael Usher via TUHS [this message]
2020-07-08 2:09 ` Dave Horsfall
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='CACg3+DG8sfarqWZM5N3Yijc0dH6LzVtYJtMG+PYTV=Dem6+2tQ@mail.gmail.com' \
--to=tuhs@minnie.tuhs.org \
--cc=dugo@xs4all.nl \
--cc=musher@ucsc.edu \
/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).