From: Bart Schaefer <barton.schaefer@gmail.com>
To: "Sup-talk@rubyforge.org" <sup-talk@rubyforge.org>
Subject: [sup-talk] Justin Mason reviews sup on his blog
Date: Fri, 18 Dec 2009 20:24:40 -0800 [thread overview]
Message-ID: <6bb609560912182024i3f8cd55fufb1cd90bcd5eb299@mail.gmail.com> (raw)
Yes, the Justin Mason who heads up the SpamAssassin project.
http://taint.org/2009/12/18/005520a.html
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next reply other threads:[~2009-12-19 4:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-19 4:24 Bart Schaefer [this message]
2009-12-19 17:09 ` William Morgan
2009-12-21 14:30 ` Justin Mason
2009-12-21 14:38 ` William Morgan
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=6bb609560912182024i3f8cd55fufb1cd90bcd5eb299@mail.gmail.com \
--to=barton.schaefer@gmail.com \
--cc=sup-talk@rubyforge.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