From: Steve Linberg <slinberg@crocker.com>
Subject: Re: Question / feature request (?)
Date: Tue, 04 May 2004 14:34:36 GMT [thread overview]
Message-ID: <slinberg-84D5F9.10343604052004@netnews.comcast.net> (raw)
In-Reply-To: <87ad0o7hvm.fsf@ursine.ca>
In article <87ad0o7hvm.fsf@ursine.ca>, Paul Johnson <baloo@ursine.ca>
wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Steve Linberg <slinberg@crocker.com> writes:
>
> > I'd like to be able to just kill all descendents of a killfiled post, in
> > other words, obviously subject to a reasonable limit of cached article
> > numbers. For my specific purposes, a week's worth - maybe a thousand or
> > two - would probably be sufficient.
>
> Kill by thread.
Well, I do already, but it's tedious work given the sheer volume in this
group.
What I basically want is to be able to just say: automatically kill any
thread started by anyone in the killfile. Not just the parent post, but
all of the replies too.
prev parent reply other threads:[~2004-05-04 14:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <slinberg-F9046F.21191503052004@netnews.comcast.net>
2004-05-04 7:48 ` Paul Johnson
2004-05-04 14:34 ` Steve Linberg [this message]
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=slinberg-84D5F9.10343604052004@netnews.comcast.net \
--to=slinberg@crocker.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 NNTP newsgroup(s).