From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.204.162.205 with SMTP id w13cs26789bkx; Mon, 9 Aug 2010 09:03:15 -0700 (PDT) Received: by 10.142.156.14 with SMTP id d14mr13746531wfe.267.1281369794094; Mon, 09 Aug 2010 09:03:14 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id q12si2690438vcy.64.2010.08.09.09.03.13; Mon, 09 Aug 2010 09:03:14 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-talk-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-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org; dkim=neutral (body hash did not verify) header.i=@messagingengine.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 488DA18583A4; Mon, 9 Aug 2010 12:03:13 -0400 (EDT) X-Greylist: delayed 348 seconds by postgrey-1.31 at rubyforge.org; Mon, 09 Aug 2010 11:44:07 EDT Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by rubyforge.org (Postfix) with ESMTP id 1F9801858394 for ; Mon, 9 Aug 2010 11:44:06 -0400 (EDT) Received: from compute1.internal (compute1.internal [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id 333CC1A2932 for ; Mon, 9 Aug 2010 11:38:06 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Mon, 09 Aug 2010 11:38:06 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=date:from:to:subject:in-reply-to:message-id:references:mime-version:content-type; s=smtpout; bh=7Sp43K70SZtlQe405EBe6qc5v48=; b=QjoCRmpoL1wId6oPny5VvpLfgtveP6JfNtMvDHAIESl7EtcUCZBaWtPcHe9C4MI1nOGMaEAWx5DWI5ukzxoY1U8iqwwhokUnCyJjOoX65GQ/g7lRYd5O1nm1rsVuR55NbKGI5fa4yKUujjchkDUR5kWBi+GxxCDovLse/8g9yOc= X-Sasl-enc: EjCoOVvVdikGS/FswGNiqZ+GG7gtuEhMSNhwrDtTJb9S 1281368285 Received: from SYSOPWEG.PHYS.CMU.EDU (SYSOPWEG.PHYS.CMU.EDU [128.2.52.109]) by mail.messagingengine.com (Postfix) with ESMTPSA id BF3F2765F4 for ; Mon, 9 Aug 2010 11:38:05 -0400 (EDT) Date: Mon, 9 Aug 2010 11:38:05 -0400 (EDT) From: Erik Quaeghebeur To: sup-talk In-Reply-To: <1281361742-sup-3674@pinkfloyd.chass.utoronto.ca> Message-ID: References: <1281349768-sup-7718@aurigae120.hi.inet> <1281361742-sup-3674@pinkfloyd.chass.utoronto.ca> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Subject: Re: [sup-talk] how to unlink a message from a thread? X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org On Mon, 9 Aug 2010, Ben Walton wrote: > > The other feature that would be really cool is to split a thread. I > interact with several people that will start a new email conversation > by opening an old message, changing subject (and maybe recipients) and > then sending it. This preserves the old headers, which sees sup > append the now disjoint new topic to the old thread. This, and the even more difficult multi-subject-mails that generate different threads (all one big thread by header...). Dealing nicely with that would mean that selected messages can be part of different (split) threads. Erik _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk