From: Adam Thornton <athornton@gmail.com>
To: Grant Taylor <gtaylor@tnetconsulting.net>
Cc: The Unix Heritage Society <tuhs@minnie.tuhs.org>,
COFF <coff@minnie.tuhs.org>
Subject: Re: [TUHS] [COFF] Topics...
Date: Mon, 6 Jul 2020 19:56:53 -0700 [thread overview]
Message-ID: <42645CD9-E6FE-4F03-9D74-AD830409A62F@gmail.com> (raw)
In-Reply-To: <8af3a571-aeb5-21fc-0041-be8649e3f9ba@spamtrap.tnetconsulting.net>
> On Jul 6, 2020, at 7:11 PM, Grant Taylor via COFF <coff@minnie.tuhs.org> wrote:
>
> On 7/6/20 7:30 PM, Greg 'groggy' Lehey wrote:
>> People (not just Clem), when you change the topic, can you please modify the Subject: to match? I'm not overly interested in uucp, but editors are a completely different matter. I'm sure I'm not the only one, so many interested parties will miss these replies.
>
> I see this type of change happen — in my not so humble opinion — /way/ /too/ /often/.
>
> 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.
>
> I'm assuming that TUHS and COFF are still on Mailman mailing lists and that Warren would be amicable to such.
>
> 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.
Meh.
These lists aren’t so high-traffic that I feel a need to, but if it happens it won’t bother me.
Adam
next prev parent reply other threads:[~2020-07-07 2:59 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 ` Adam Thornton [this message]
2020-07-07 14:33 ` 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
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=42645CD9-E6FE-4F03-9D74-AD830409A62F@gmail.com \
--to=athornton@gmail.com \
--cc=coff@minnie.tuhs.org \
--cc=gtaylor@tnetconsulting.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).