From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.86.59.13 with SMTP id h13cs50508fga; Mon, 22 Feb 2010 06:01:04 -0800 (PST) Received: by 10.224.43.157 with SMTP id w29mr6013056qae.313.1266847263096; Mon, 22 Feb 2010 06:01:03 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 5si4819378qwg.18.2010.02.22.06.01.02; Mon, 22 Feb 2010 06:01:03 -0800 (PST) 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; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 778551858302; Mon, 22 Feb 2010 09:01:02 -0500 (EST) Received: from mail-ew0-f212.google.com (mail-ew0-f212.google.com [209.85.219.212]) by rubyforge.org (Postfix) with ESMTP id 2270418582F9; Mon, 22 Feb 2010 09:00:55 -0500 (EST) Received: by ewy4 with SMTP id 4so216590ewy.7 for ; Mon, 22 Feb 2010 06:00:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:notmuch-help :notmuch-help:notmuch-help:notmuch-help:from:subject:to:in-reply-to :references; bh=dxNhNZv8Hd97HPtTiJ2A04ICa+pnT8plEb9UsDZhWJo=; b=mzVxoOy+0sVxSKgqg+KT8zFc5VXrDCUNX926GMhXPQOVRRUrMAdiIEtbsp5ZfisxSJ uCf4hoNBbY69KUxzYYejD7iPmoGmRZIaScV5jogRBus37kJltp1yI2h+Z/y4t1WY2NLF msfqOELBqXe9mmYjVhVnUF9zibv3WIUCyNpS4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:notmuch-help:from:subject:to:in-reply-to:references; b=gOpnCIfgYT6CeVCv+GH2+sWAf89R/wvwoeCzv/zErau8FuxBx87lykoVoxoWHMcy6g vDhrJtONhDy5M1dDMgQ8pNF1upNgXbemkFMy80kodWlhxcDH3d7iXvN8BTyqpWZ7wovN UOjNeu0nGBdtD/lQaP3TXL4TOpoqG4m8w+lC8= Received: by 10.213.1.210 with SMTP id 18mr4591253ebg.58.1266847255200; Mon, 22 Feb 2010 06:00:55 -0800 (PST) Received: from localhost (ks.feydakins.org [91.121.104.209]) by mx.google.com with ESMTPS id 14sm2423775ewy.11.2010.02.22.06.00.53 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 22 Feb 2010 06:00:53 -0800 (PST) Message-ID: <4b828e15.0e67f10a.21cd.ffffc19d@mx.google.com> Date: Mon, 22 Feb 2010 06:00:53 -0800 (PST) Notmuch-Help: ,a - attach a file Notmuch-Help: ,s - send the message (Notmuch-Help lines will be removed) Notmuch-Help: ,q - abort the message Notmuch-Help: - skip through header lines From: Nicolas Pouillard To: Sup developer discussion , Sup developer discussion In-Reply-To: <20100221192947.GA16075@mjolnir> References: <20100218114943.GB911@mjolnir> <1266730498-sup-78@tilus.net> <20100221134249.GA11429@mjolnir> <4b8172dc.0f67f10a.4111.7dce@mx.google.com> <20100221192947.GA16075@mjolnir> Subject: Re: [sup-devel] email threading - tree vs. graph X-BeenThere: sup-devel@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Sup developer discussion List-Id: Sup developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 On Sun, 21 Feb 2010 14:29:47 -0500, "W. Trevor King" wrote: > On Sun, Feb 21, 2010 at 09:52:28AM -0800, Nicolas Pouillard wrote: > > On Sun, 21 Feb 2010 08:42:49 -0500, "W. Trevor King" wrote: > > > On Sun, Feb 21, 2010 at 08:38:35AM +0200, Tero Tilus wrote: > > [...] > > > > Have a pointer to code? > > > > > > My code is currently stuffed into an in-transition BE project, but it > > > should be easy to separate. Grab the whole repo with Bazaar: > > > bzr branch http://www.physics.drexel.edu/~wking/code/bzr/be.mailing-list > > > Graphing module is libbe/util/graph.py. My very minimal browser is > > > misc/mailbox-tools/mailgraph.py. Set up the BE version file with > > > cd be.mailing-list > > > make libbe/_version.py > > > and run the browser with > > > misc/mailbox-tools/mailgraph.py *.mbox > > > Press 'h' for help. > > > > I've tried your program on a 100 messages mbox and got this: > > > > missing Message-ID: > > ... > > You probably had a bunch of emails in you mbox with > In-Reply-To: > But no message(s) with > Message-ID: > > If mailgraph.py can't find the parent message, it prints that warning > and continues, so you can probably just ignore it. > > > Traceback (most recent call last): > > ... > > libbe.util.graph.CyclicGraph: 3 of 100 elements not reachable from tips > > You have a cyclic reference in your mbox somewhere. I've added some > really inefficient code to actually *find* cycles (rather than just > deducing their existence) and print useful error messages. Pull my > current repo and try: > > $ misc/mailbox-tools/mailgraph.py --check-for-cycle *.mbox > > Then you'll have to go through the mbox (or a copy) by hand and break > the cycle. The check only finds one cycle at a time, so you may need > to iterate... I get: ... libbe.util.graph.CyclicGraphError: cycle detected: Sun, 21 Fe Reinier Lamers [darcs-users] [patch167] Reintroduce UTF-8 tagging... Sun, 21 Fe Reinier Lamers [darcs-users] [patch167] Reintroduce UTF-8 tagging... Actually the mentioned mail have Message-ID equals to In-Reply-To. While I'm reporting this issue and thus won't get any such messages, it would be "nice" to have a more robust behavior in case of cycles. In particular these auto-cycles can be just ignored. -- Nicolas Pouillard http://nicolaspouillard.fr _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel