From mboxrd@z Thu Jan  1 00:00:00 1970
Received: by 10.213.13.12 with SMTP id z12cs283721ebz;
        Sat, 9 Jan 2010 14:47:28 -0800 (PST)
Received: by 10.224.80.91 with SMTP id s27mr15562208qak.271.1263077247104;
        Sat, 09 Jan 2010 14:47:27 -0800 (PST)
Return-Path: <sup-talk-bounces@rubyforge.org>
Received: from rubyforge.org (rubyforge.org [205.234.109.19])
        by mx.google.com with ESMTP id 6si6768364qwk.1.2010.01.09.14.47.26;
        Sat, 09 Jan 2010 14:47:27 -0800 (PST)
Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org
Received: from rubyforge.org (rubyforge.org [127.0.0.1])
	by rubyforge.org (Postfix) with ESMTP id 6EF1D1779941;
	Sat,  9 Jan 2010 17:47:26 -0500 (EST)
Received: from kuovi.tilus.net (kuovi.tilus.net [80.68.89.168])
	by rubyforge.org (Postfix) with ESMTP id 4F78318582C2
	for <sup-talk@rubyforge.org>; Sat,  9 Jan 2010 17:47:17 -0500 (EST)
Received: by kuovi.tilus.net (Postfix, from userid 1000)
	id 9CDAB6011; Sun, 10 Jan 2010 00:47:16 +0200 (EET)
From: Tero Tilus <tero@tilus.net>
To: sup-talk <sup-talk@rubyforge.org>
In-reply-to: <3f81a4241001080800ja97a0bbm9c9c39504ed88bec@mail.gmail.com>
References: <f4cc59760907010248r5598eb50sf29b3ae8f500e5f8@mail.gmail.com>
	<f4cc59760907020314o60100e01r1a1f8af4d354030a@mail.gmail.com>
	<1246542975-sup-7239@ntdws12.chass.utoronto.ca>
	<3f81a4241001041055t443931c6vbbe1e7a44599d4f1@mail.gmail.com>
	<1262728264-sup-3239@masanjin.net>
	<3f81a4241001061118k7fa0c9e6ub556c400a00b139b@mail.gmail.com>
	<1262805923-sup-3586@masanjin.net> <1262811731-sup-2447@tilus.net>
	<1262812952-sup-9357@masanjin.net> <1262879727-sup-9702@tilus.net>
	<3f81a4241001080800ja97a0bbm9c9c39504ed88bec@mail.gmail.com>
Date: Sun, 10 Jan 2010 00:47:16 +0200
Message-Id: <1263076756-sup-4633@tilus.net>
User-Agent: Sup/git
Subject: Re: [sup-talk] sent_source - singular or per-account?
X-BeenThere: sup-talk@rubyforge.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: User & developer discussion of Sup <sup-talk.rubyforge.org>
List-Unsubscribe: <http://rubyforge.org/mailman/options/sup-talk>,
	<mailto:sup-talk-request@rubyforge.org?subject=unsubscribe>
List-Archive: <http://rubyforge.org/pipermail/sup-talk>
List-Post: <mailto:sup-talk@rubyforge.org>
List-Help: <mailto:sup-talk-request@rubyforge.org?subject=help>
List-Subscribe: <http://rubyforge.org/mailman/listinfo/sup-talk>,
	<mailto:sup-talk-request@rubyforge.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sup-talk-bounces@rubyforge.org
Errors-To: sup-talk-bounces@rubyforge.org

Bryan Richardson, 2010-01-08 18:00:
> I guess the first question I should really ask is if Tero is going
> to take a stab at this or if I should... :)

Make your choise and take your stab.  I'll be a happy user of
sent_source selection, be it hook or conf based.

I've already got a long enough backlog of features I want to hack
with.

-- 
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk