From: bwalton@artsci.utoronto.ca (Ben Walton)
Subject: [sup-talk] flexible sent source (update)
Date: Thu, 07 May 2009 18:01:16 -0400 [thread overview]
Message-ID: <1241733502-sup-26@ntdws12.chass.utoronto.ca> (raw)
Hi All,
I've pushed a few new changes to the bw/flexible_sent branch at
git://code.chass.utoronto.ca/bwalton-sup.git. It is now possible to
use sup-config to choose which (valid) mail source to store messages
in and I tweaked how the special sent label is applied.
I'd appreciate it if those interested in the topic played with this
branch. William, I'd also appreciate any feedback you have on it at
this point. (Do you mind pulling my branch, or would you prefer a
git-send-email stack of patches?)
I still need to tackle mbox locking...
Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302
GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu
Contact me to arrange for a CAcert assurance meeting.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090507/b2a65479/attachment.bin>
next reply other threads:[~2009-05-07 22:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 22:01 Ben Walton [this message]
2009-05-13 18:11 ` William Morgan
2009-05-13 18:50 ` Ben Walton
2009-05-13 18:55 ` 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=1241733502-sup-26@ntdws12.chass.utoronto.ca \
--to=bwalton@artsci.utoronto.ca \
/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