Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] sup-server revisited
Date: Wed, 23 Feb 2011 18:30:26 -0300	[thread overview]
Message-ID: <1298496576-sup-8044@alvh.no-ip.org> (raw)
In-Reply-To: <1298495002-sup-1617@masanjin.net>

Excerpts from William Morgan's message of mié feb 23 18:08:07 -0300 2011:
> Reformatted excerpts from Alvaro Herrera's message of 2011-02-23:
> > I like this, except the part that thread_labels = union(states).  It
> > doesn't work correctly for "attachment" for example: it makes it look
> > like the whole thread "has attachments" which doesn't make sense.
> 
> The thread has the label "attachment", but when you look at the
> individual messages inside of it, you see which ones actually have the
> attachment state. I think this makes sense.

Yes, this sounds good to me.

> > Also, you said upthread that Heliotrope was going to provide ways to
> > break threads and form new ones from pieces.  I badly want this
> > feature :-)  (I haven't checked Heliotrope out yet).
> 
> Yes, this will definitely be there.

Great.

-- 
Álvaro Herrera <alvherre@alvh.no-ip.org>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel

  reply	other threads:[~2011-02-23 21:53 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
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 [this message]
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=1298496576-sup-8044@alvh.no-ip.org \
    --to=alvherre@alvh.no-ip.org \
    --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