From: marcus-sup@bar-coded.net (Marcus Williams)
Subject: [sup-talk] Spam hooks.
Date: Thu, 10 Apr 2008 12:04:32 +0100 [thread overview]
Message-ID: <1207825216-sup-4659@tomsk> (raw)
In-Reply-To: <1207823540-sup-3480@tomsk>
On 10.4.2008, I wrote:
> On 9.4.2008, Richard Heycock wrote:
> > That would be great. I just need the basic idea and I should be able
> > to take it form there.
>
> ... patch is winging its way to sup-talk as I write this. Its against
> next but it should patch cleanly against master. Some quick pointers
> for the mark-as-spam.rb:
Note that perhaps I should also add that this hook gets run on "toggle"
of the spam flag. So you probably want to check which way its been
toggled by looking for the :spam flag in the labels set if you want to
be extra careful. I think you can probably just use the thread
object's labels to do this.
Marcus
next prev parent reply other threads:[~2008-04-10 11:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-09 10:07 Richard Heycock
2008-04-09 10:19 ` Ian Taylor
2008-04-09 20:00 ` Marcus Williams
2008-04-09 21:08 ` Richard Heycock
2008-04-10 10:37 ` Marcus Williams
2008-04-10 11:04 ` Marcus Williams [this message]
2008-04-10 13:09 ` Richard Heycock
2008-04-10 4:05 ` William Morgan
2008-04-10 13:05 ` Richard Heycock
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=1207825216-sup-4659@tomsk \
--to=marcus-sup@bar-coded.net \
/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