From: Tero Tilus <tero@tilus.net>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Toggling usual status of sources
Date: Wed, 12 May 2010 07:44:29 +0300 [thread overview]
Message-ID: <1273637602-sup-1446@tilus.net> (raw)
In-Reply-To: <4BE9F632.3020108@cquest.utoronto.ca>
Ben Walton, 2010-05-12 03:28:
> #toggle usual status on previous source
> [...]
> I don't see a way, currently, to toggle that flag. Would there be
> objections to adding support for that? Is what I'm proposing _too_
> nuts?
Not at all. If you do that, I'll switch to rotating inbox.
> [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 think rotating inbox would pretty clean to implement using either
"virtual" or "meta" source. If either of them ever got implemented.
--
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2010-05-12 4:51 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 [this message]
2010-05-13 14:15 ` Ben Walton
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=1273637602-sup-1446@tilus.net \
--to=tero@tilus.net \
--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