Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] sent_source - singular or per-account?
Date: Wed, 06 Jan 2010 16:23:41 -0500	[thread overview]
Message-ID: <1262812952-sup-9357@masanjin.net> (raw)
In-Reply-To: <1262811731-sup-2447@tilus.net>

Reformatted excerpts from Tero Tilus's message of 2010-01-06:
> Does it really need to be a hook?  I haven't seen a single use case
> justifying hook over simply having per-account sent_source in
> config.yaml.

No, I don't care which it is. But you will be responsible for helping
the first person who wants to automatically choose their sent source
based on the body of the message. :)
-- 
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  reply	other threads:[~2010-01-06 21:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-01  9:48 Jim Cheetham
2009-07-01 19:39 ` Ben Walton
2009-07-02  2:30   ` Jim Cheetham
2009-07-02  3:17     ` Ben Walton
2009-07-02 10:14       ` Jim Cheetham
2009-07-02 14:02         ` Ben Walton
2010-01-04 18:55           ` Bryan Richardson
2010-01-05 21:51             ` William Morgan
2010-01-06 19:18               ` Bryan Richardson
2010-01-06 19:29                 ` William Morgan
2010-01-06 21:04                   ` Tero Tilus
2010-01-06 21:23                     ` William Morgan [this message]
2010-01-07 15:58                       ` Tero Tilus
2010-01-08 16:00                         ` Bryan Richardson
2010-01-09 22:47                           ` Tero Tilus
2010-01-12 21:38                             ` Bryan Richardson
2010-01-12 23:10                               ` Tero Tilus
2010-01-04 20:50   ` Tero Tilus
2010-01-08 23:06 ` Kevin Riggle

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=1262812952-sup-9357@masanjin.net \
    --to=wmorgan-sup@masanjin.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