From: Tomasz Rola <rtomek@ceti.pl>
To: COFF <coff@minnie.tuhs.org>
Cc: Grant Taylor via TUHS <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Topics...
Date: Tue, 7 Jul 2020 16:33:40 +0200 [thread overview]
Message-ID: <20200707143340.GA20201@tau1.ceti.pl> (raw)
In-Reply-To: <8af3a571-aeb5-21fc-0041-be8649e3f9ba@spamtrap.tnetconsulting.net>
On Mon, Jul 06, 2020 at 08:11:43PM -0600, Grant Taylor via TUHS 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 just trying to gauge people's interest in this idea.
I would not care. I would want to get everything, because one day my
interests could change (I might want to know what people said about
editors, for example :-) ) and who knows, maybe a list would be gone
already. I even archive the spam, just in case I want to do some big
data stuff on it one day. My yearly mailbox is on par with two cdroms,
so any savings would be rather minimal.
And boy, the more the better. Just think about those scripts to
process (hundred) thousands of mails. Displaying stuff on text
terminal. Green text terminal emulator. Better than norp, if you ask
me. Actually, this is norp.
--
Regards,
Tomasz Rola
--
** A C programmer asked whether computer had Buddha's nature. **
** As the answer, master did "rm -rif" on the programmer's home **
** directory. And then the C programmer became enlightened... **
** **
** Tomasz Rola mailto:tomasz_rola@bigfoot.com **
next prev parent reply other threads:[~2020-07-07 14:41 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 ` Tomasz Rola [this message]
2020-07-07 14:38 ` [TUHS] Topics 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
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=20200707143340.GA20201@tau1.ceti.pl \
--to=rtomek@ceti.pl \
--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).