From: "Dave Korn" <dave.korn@artimi.com>
To: "'a modest proposal'" <cygwin-talk@cygwin.com>
Subject: RE: A banner day
Date: Thu, 20 Apr 2006 09:27:00 -0000 [thread overview]
Message-ID: <015c01c6645c$951a1080$a501a8c0@CAM.ARTIMI.COM> (raw)
In-Reply-To: <20060420061142.GA9303@trixie.casa.cgf.cx>
On 20 April 2006 07:12, Christopher Faylor wrote:
> sending off-topic messages in one form or another.
> I gave each of these people 3 or 4 warnings before blocking them and,
> Usually when I block someone, I block them from all of the cygwin lists.
> But, tonight, I have chosen to only block Gary R. Van Sickle from the
> cygwin-apps list. Maybe when I wake up tomorrow, I will conclude that
> this was a big mistake because, after all, Gary does sometimes provide
> useful technical feedback.
> Anyway, if anyone has a problem with my decision,
This post is not about the rightness or wrongness of that decision in this
particular case, but a suggestion for a half-way measure to use in such
circumstances: if the problem is repeated OT posting, and they refuse to
TITTTL it, which is the proper thing to do if you want to pursue an OT thread,
then you could just as well put all their posts on auto-redirect to this group
rather than ban them altogether. This would only make sense as a temporary
measure but it would let people get it (whatever 'it' might be on that
particular occasion) out of their system and once the thread had finally died
away the auto-redirect could be turned off again.
cheers,
DaveK
--
Can't think of a witty .sigline today....
next prev parent reply other threads:[~2006-04-20 9:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 6:11 Christopher Faylor
2006-04-20 9:27 ` Dave Korn [this message]
2006-04-20 15:24 ` Christopher Faylor
2006-04-20 12:25 ` Arbitraily Banning Maintainers From Mailing Lists Which They Need To Perform Their Duties Gary R. Van Sickle
2006-04-20 12:47 ` Dave Korn
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='015c01c6645c$951a1080$a501a8c0@CAM.ARTIMI.COM' \
--to=dave.korn@artimi.com \
--cc=cygwin-talk@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).