Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Nicolas Pouillard <nicolas.pouillard@gmail.com>
To: William Morgan <wmorgan-sup@masanjin.net>,
	sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] sup-server revisited
Date: Wed, 23 Feb 2011 01:48:12 -0800 (PST)	[thread overview]
Message-ID: <4d64d7dc.5989cc0a.4550.ffffb543@mx.google.com> (raw)
In-Reply-To: <1298409714-sup-1926@masanjin.net>

On Tue, 22 Feb 2011 21:29:07 +0000, William Morgan <wmorgan-sup@masanjin.net> wrote:
> Reformatted excerpts from Tero Tilus's message of 2011-02-22:
> > I guess this offers the possibility to add threading to "external state"
> > of messages, together with labels.  I'd do a whole a lot of more
> > prune'n'crafting with my threads if there only was more comfortable
> > interface to doing it (admit it, been too lazy to implement it in sup).
> 
> Not quite sure I follow, but the intention is certainly to allow clients to
> create and break threads and to present labels as per-thread, rather than
> per-message, data.

I would not go for "labels on threads" only, here is a list of labels that are
more message based than thread based: unread, starred, draft, sent,
attachment. And while it would make sense to have special cases for those this
also prevents from user defined per message labels.

-- 
Nicolas Pouillard
http://nicolaspouillard.fr
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel


  reply	other threads:[~2011-02-23 10:10 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-21 21:02 William Morgan
2011-02-22 13:46 ` Mark Alexander
2011-02-22 17:55   ` William Morgan
2011-02-22 18:44     ` Tero Tilus
2011-02-22 19:00       ` William Morgan
2011-02-22 14:09 ` Nicolas Pouillard
2011-02-22 20:17 ` Tero Tilus
2011-02-22 21:29   ` William Morgan
2011-02-23  9:48     ` Nicolas Pouillard [this message]
2011-02-23 18:43       ` William Morgan
2011-02-23 18:53         ` Alvaro Herrera
2011-02-23 21:08           ` William Morgan
2011-02-23 21:30             ` Alvaro Herrera
2011-03-03 19:38         ` Sascha Silbe
2011-02-26 19:15 ` Hamish
2011-02-26 22:04   ` William Morgan
2011-02-26 23:15     ` William Morgan
2011-03-01 19:38       ` Hamish
2011-03-02 12:43         ` Gregor Hoffleit
2011-03-02 18:51           ` William Morgan
2011-03-03 17:32             ` Gregor Hoffleit
2011-03-03 19:17               ` William Morgan
2011-04-15 10:46                 ` Gregor Hoffleit
2011-04-15 17:16                   ` William Morgan
2011-04-15 20:53                     ` Gregor Hoffleit
2011-04-17 16:58                   ` William Morgan
2011-04-17 17: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=4d64d7dc.5989cc0a.4550.ffffb543@mx.google.com \
    --to=nicolas.pouillard@gmail.com \
    --cc=sup-devel@rubyforge.org \
    --cc=wmorgan-sup@masanjin.net \
    /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