From mboxrd@z Thu Jan  1 00:00:00 1970
Received: by 10.142.178.13 with SMTP id a13cs38124wff;
        Sun, 22 May 2011 15:22:22 -0700 (PDT)
Received: by 10.52.179.230 with SMTP id dj6mr2520884vdc.130.1306102942064;
        Sun, 22 May 2011 15:22:22 -0700 (PDT)
Return-Path: <sup-devel-bounces@rubyforge.org>
Received: from rubyforge.org (rubyforge.org [205.234.109.19])
        by mx.google.com with ESMTP id ei9si4013606vdb.136.2011.05.22.15.22.20;
        Sun, 22 May 2011 15:22:21 -0700 (PDT)
Received-SPF: pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org
Received: from rubyforge.org (rubyforge.org [127.0.0.1])
	by rubyforge.org (Postfix) with ESMTP id 9B8561858361
	for <eg@gaute.vetsj.com>; Sun, 22 May 2011 18:22:20 -0400 (EDT)
Received: from masanjin.net (masanjin.net [209.20.72.13])
	by rubyforge.org (Postfix) with ESMTP id A571A1858112
	for <sup-devel@rubyforge.org>; Sun, 22 May 2011 17:58:13 -0400 (EDT)
Received: from w by masanjin.net with local (Exim 4.71)
	(envelope-from <w@masanjin.net>) id 1QOGmb-0003sH-TA
	for sup-devel@rubyforge.org; Sun, 22 May 2011 22:05:57 +0000
From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-devel <sup-devel@rubyforge.org>
In-reply-to: <1305748878-sup-7940@xo15-sascha.sascha.silbe.org>
References: <BANLkTi=bSNyp+8XFCRpYGojuM8Ub5PjB2A@mail.gmail.com>
	<1305471101-sup-6655@masanjin.net>
	<BANLkTin5eRZw44Je+==V=K4pyVw2T7S3+A@mail.gmail.com>
	<1305693289-sup-4896@masanjin.net>
	<1305748878-sup-7940@xo15-sascha.sascha.silbe.org>
Date: Sun, 22 May 2011 22:05:57 +0000
Message-Id: <1306101722-sup-3610@masanjin.net>
User-Agent: Sup/git
Subject: Re: [sup-devel] Query for largest msg_id?
X-BeenThere: sup-devel@rubyforge.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Sup developer discussion <sup-devel@rubyforge.org>
List-Id: Sup developer discussion <sup-devel.rubyforge.org>
List-Unsubscribe: <http://rubyforge.org/mailman/options/sup-devel>,
	<mailto:sup-devel-request@rubyforge.org?subject=unsubscribe>
List-Archive: <http://rubyforge.org/pipermail/sup-devel>
List-Post: <mailto:sup-devel@rubyforge.org>
List-Help: <mailto:sup-devel-request@rubyforge.org?subject=help>
List-Subscribe: <http://rubyforge.org/mailman/listinfo/sup-devel>,
	<mailto:sup-devel-request@rubyforge.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sup-devel-bounces@rubyforge.org
Errors-To: sup-devel-bounces@rubyforge.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