Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: John Bent <johnbent@lanl.gov>
To: sup-talk <sup-talk@rubyforge.org>
Subject: [sup-talk] Send Individually feature
Date: Thu, 08 Jul 2010 17:15:50 -0600	[thread overview]
Message-ID: <1278630818-sup-6829@guava.lanl.gov> (raw)

I'm sorry I just contribute wishes and not patches . . . 

Speaking of which, here's a wish!

I sometimes send email to large recipient lists.  I would really like
there to be a way to ask sup to send a separate email to each recipient
instead of just sending the same one to all.  I want to break the
problem of diffused responsibility.  Also, when I'm sending out
invitations, I feel the acceptance rate is higher when people receive an
individual email. bcc'ing also doesn't work because I want them to be
tricked into thinking that I've sent them an individualized email. 
-- 
Thanks,

John 
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


             reply	other threads:[~2010-07-08 23:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-08 23:15 John Bent [this message]
2011-01-18 17:34 ` Sascha Silbe

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=1278630818-sup-6829@guava.lanl.gov \
    --to=johnbent@lanl.gov \
    --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