From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Spam hooks.
Date: Wed, 09 Apr 2008 21:05:55 -0700 [thread overview]
Message-ID: <1207800329-sup-6044@south> (raw)
In-Reply-To: <1207771005-sup-8074@tomsk>
Reformatted excerpts from Marcus Williams's message of 2008-04-09:
> In my local edits I have a hook that allows for this, but its not
> going to forward anything for you - it leaves it up to you to do what
> you want with the thread. It wouldnt be that hard to iterate over the
> thread and forward all messages to an address in ruby though.
I'd be happy to merge in such a hook if you want to send a patch.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2008-04-10 4:05 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
2008-04-10 13:09 ` Richard Heycock
2008-04-10 4:05 ` William Morgan [this message]
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=1207800329-sup-6044@south \
--to=wmorgan-sup@masanjin.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