From: "Alan D. Salewski" <salewski@att.net>
To: The Unix Heritage Society <tuhs@minnie.tuhs.org>
Cc: COFF <coff@minnie.tuhs.org>
Subject: Re: [TUHS] Topics...
Date: Tue, 7 Jul 2020 10:38:43 -0400 [thread overview]
Message-ID: <20200707143843.GI11130@att.net> (raw)
In-Reply-To: <8af3a571-aeb5-21fc-0041-be8649e3f9ba@spamtrap.tnetconsulting.net>
On 2020-07-06 20:11:43, Grant Taylor via TUHS spake thus:
[...]
> So, I'm wondering if people are interested in configuring TUHS and / or COFF
> mailing list (Mailman) with topics. That way people could subscribe to the
> topics that they are interested in and not receive copies of topics they
> aren't interested in.
[...]
> To clarify, it would still be the same mailing list(s) as they exist today.
> They would just have the to be utilized option of picking interesting
> topics. Where topics would be based on keywords in the message body.
>
> I'm just trying to gauge people's interest in this idea.
My preference would be to keep things the way they are.
I want to receive all list messages; I would not want to switch to an
arrangement where I was in danger of missing messages because my list
preferences config became a little stale.
-Al
--
-----------------------------------------------------------------
a l a n d. s a l e w s k i salewski@att.net
1024D/FA2C3588 EDFA 195F EDF1 0933 1002 6396 7C92 5CB3 FA2C 3588
-----------------------------------------------------------------
next prev parent reply other threads:[~2020-07-07 14:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 2:11 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 [this message]
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
2020-07-08 2:09 ` Dave Horsfall
2020-07-07 16:16 [TUHS] Topics Norman Wilson
2020-07-08 13:06 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=20200707143843.GI11130@att.net \
--to=salewski@att.net \
--cc=coff@minnie.tuhs.org \
--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).