From: Justin Mason <jm@jmason.org>
To: William Morgan <wmorgan-sup@masanjin.net>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Justin Mason reviews sup on his blog
Date: Mon, 21 Dec 2009 14:30:26 +0000 [thread overview]
Message-ID: <6c399e450912210630x572b2131xb143fd3b28cd8404@mail.gmail.com> (raw)
In-Reply-To: <1261242535-sup-932@masanjin.net>
On Sat, Dec 19, 2009 at 17:09, William Morgan <wmorgan-sup@masanjin.net> wrote:
> Reformatted excerpts from Bart Schaefer's message of 2009-12-18:
>> Yes, the Justin Mason who heads up the SpamAssassin project.
>>
>> http://taint.org/2009/12/18/005520a.html
>
> Cool! All very valid criticisms.
cheers! I _am_ really enjoying sup, btw ;) Thanks for writing it!
--
--j.
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2009-12-21 14:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-19 4:24 Bart Schaefer
2009-12-19 17:09 ` William Morgan
2009-12-21 14:30 ` Justin Mason [this message]
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=6c399e450912210630x572b2131xb143fd3b28cd8404@mail.gmail.com \
--to=jm@jmason.org \
--cc=sup-talk@rubyforge.org \
--cc=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