Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Query for largest msg_id?
Date: Sun, 22 May 2011 22:05:57 +0000	[thread overview]
Message-ID: <1306101722-sup-3610@masanjin.net> (raw)
In-Reply-To: <1305748878-sup-7940@xo15-sascha.sascha.silbe.org>

Reformatted excerpts from Sascha Silbe's message of 2011-05-18:
> If heliotrope permanently erases the copies (instead of just not
> exposing UI to access them), that would be a major step backwards.

What do you suggest as a way of exposing duplicates within the UI? I
worry that just keeping all copies of a message around will make the
thread structure messy. Is there a better alternative?
-- 
William <wmorgan-sup@masanjin.net>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel


  parent reply	other threads:[~2011-05-22 22:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-10 15:17 Horacio Sanson
2011-05-15 15:01 ` William Morgan
2011-05-16 15:02   ` Horacio Sanson
2011-05-17 14:59     ` Horacio Sanson
2011-05-17 15:15       ` Horacio Sanson
2011-05-18  5:05       ` William Morgan
2011-05-20 15:38         ` Horacio Sanson
2011-05-22 22:00           ` William Morgan
2011-05-23 21:22           ` Hamish
2011-05-24  3:16             ` Horacio Sanson
2011-05-18  4:59     ` William Morgan
2011-05-18 20:09       ` Sascha Silbe
2011-05-19  3:14         ` Alvaro Herrera
2011-05-22 22:05         ` William Morgan [this message]
2011-05-23  7:52           ` Gaudenz Steinlin
2011-05-23 16:14             ` 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=1306101722-sup-3610@masanjin.net \
    --to=wmorgan-sup@masanjin.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