From: Ben Walton <bwalton@artsci.utoronto.ca>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Toggling usual status of sources
Date: Thu, 13 May 2010 10:15:06 -0400 [thread overview]
Message-ID: <1273759958-sup-326@pinkfloyd.chass.utoronto.ca> (raw)
In-Reply-To: <1273637602-sup-1446@tilus.net>
Excerpts from Tero Tilus's message of Wed May 12 00:44:29 -0400 2010:
> Not at all. If you do that, I'll switch to rotating inbox.
Cool!
> > [1] This is along the lines of my 'patterned/dynamic source' idea
> > that I briefly described a few nights back, but I think that was
> > eaten...
>
> Patterned/dynamic/recursive sources are in my todo-list. Haven't
> got around implementing it yet. Gave it some thought though. Did
> you consider them "virtual" (as in bunch of "physical" maildir/mbox
> stores made transparently look like one source) or "meta" (as in
> template source which sup uses to generate a set of "physical"
> sources)? Which one would be better?
I was thinking meta, but virtual is interesting too. I _think_ that
meta would be easier to implement given the current code structure. I
also think having each of the 'dynamic' sources listed explicitly in
sources.yaml has some merit.
Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
prev parent reply other threads:[~2010-05-13 15:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 0:28 Ben Walton
2010-05-12 4:44 ` Tero Tilus
2010-05-13 14:15 ` Ben Walton [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=1273759958-sup-326@pinkfloyd.chass.utoronto.ca \
--to=bwalton@artsci.utoronto.ca \
--cc=sup-devel@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