From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] [sup-devel] sup-server revisited
Date: Wed, 23 Feb 2011 18:23:33 +0000 [thread overview]
Message-ID: <1298485323-sup-5531@masanjin.net> (raw)
In-Reply-To: <4d64da8b.8389cc0a.31cf.6b21@mx.google.com>
Reformatted excerpts from Nicolas Pouillard's message of 2011-02-23:
> I agree with you and don't to expose such details. What I want is a
> way to separate the frontend from the backend completely.
Yes, absolutely.
> I also want to be able to script batch operations on the mail store
> easily.
Agreed. A definite goal. The prevalence of [bug reports about]
sup-tweak-labels usage is a sign that other people desire this too.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2011-02-23 18:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 21:02 William Morgan
2011-02-22 14:09 ` Nicolas Pouillard
2011-02-22 18:00 ` [sup-talk] " William Morgan
2011-02-23 9:59 ` Nicolas Pouillard
2011-02-23 18:23 ` William Morgan [this message]
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=1298485323-sup-5531@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