From: dave@horsfall.org (Dave Horsfall)
Subject: Mangled and non-mangled TUHS mail lists
Date: Wed, 4 Oct 2017 13:28:57 +1100 (EST) [thread overview]
Message-ID: <alpine.BSF.2.21.1710041326421.73049@aneurin.horsfall.org> (raw)
In-Reply-To: <20171003184919.1QJzu%steffen@sdaoden.eu>
On Tue, 3 Oct 2017, Steffen Nurpmeso wrote:
> |I think that modifying the subject to add a tag is a perfectly valid
> |thing. As such, provisions should make such modifications /possible/.
> |Then leave the choice of doing so or not up to each list's
> |administrator.
>
> As has happened recently. Sure.
Except Warren did it backwards; he should've left the original list as it
was, and migrated those with fussy clients to the new list.
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
next prev parent reply other threads:[~2017-10-04 2:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-01 3:25 Warren Toomey
2017-10-01 14:00 ` Clem Cole
2017-10-01 14:08 ` Don Hopkins
2017-10-02 1:01 ` Dave Horsfall
2017-10-02 8:22 ` jason-tuhs
2017-10-02 12:38 ` Steve Nickolas
2017-10-02 13:34 ` David Ryskalczyk
2017-10-03 0:51 ` Dave Horsfall
2017-10-03 2:19 ` Steve Nickolas
2017-10-03 3:25 ` Grant Taylor
2017-10-03 3:33 ` Dave Horsfall
2017-10-03 3:55 ` Grant Taylor
2017-10-03 4:17 ` Dave Horsfall
2017-10-03 4:12 ` Kurt H Maier
2017-10-03 7:40 ` Ian Zimmerman
2017-10-03 14:08 ` Steffen Nurpmeso
2017-10-03 18:20 ` Grant Taylor
2017-10-03 18:43 ` Ian Zimmerman
2017-10-03 21:59 ` Grant Taylor
2017-10-03 18:49 ` Steffen Nurpmeso
2017-10-03 21:54 ` Grant Taylor
2017-10-03 22:00 ` Mangled and non-mangled TUHS mail lists [ enough already? ] Jon Steinhart
2017-10-04 20:17 ` Mangled and non-mangled TUHS mail lists Steffen Nurpmeso
2017-10-04 2:28 ` Dave Horsfall [this message]
2017-10-04 20:59 ` Steffen Nurpmeso
2017-10-03 10:12 ` Steve Nickolas
2017-10-03 19:21 ` Bakul Shah
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=alpine.BSF.2.21.1710041326421.73049@aneurin.horsfall.org \
--to=dave@horsfall.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).