From: Tero Tilus <tero@tilus.net>
To: Sup users <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] More before-add hook issues
Date: Wed, 16 Feb 2011 11:31:17 +0200 [thread overview]
Message-ID: <1297848161-sup-8178@tilus.net> (raw)
In-Reply-To: <1297780499-sup-4885@plc.intranet.plecavalier.com>
Philippe LeCavalier, 2011-02-15 16:55:
> 8 if ! addressfile.grep(/#{message.list_address.email}/).empty?
Try
if message.list_address && !addressfile.grep(/#{message.list_address.email}/).empty?
--
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2011-02-16 10:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 14:55 Philippe LeCavalier
2011-02-16 9:31 ` Tero Tilus [this message]
2011-02-16 14:35 ` Philippe LeCavalier
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=1297848161-sup-8178@tilus.net \
--to=tero@tilus.net \
--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