From: Nicolas Pouillard <nicolas.pouillard@gmail.com>
To: Sup developer discussion <sup-devel@rubyforge.org>,
Sup developer discussion <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] email threading - tree vs. graph
Date: Mon, 22 Feb 2010 08:04:20 -0800 (PST) [thread overview]
Message-ID: <4b82ab04.1067f10a.2460.ffffc8a4@mx.google.com> (raw)
In-Reply-To: <20100222155419.GC26338@mjolnir>
On Mon, 22 Feb 2010 10:54:19 -0500, "W. Trevor King" <wking@drexel.edu> wrote:
> On Mon, Feb 22, 2010 at 06:00:53AM -0800, Nicolas Pouillard wrote:
> > ...
> > 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.
>
> Hah. That is great :p.
>
> > 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.
>
> Added a 'correct-mailbox.py' script that tries to handle all of these
> (and probably more in the future) issues in one shot.
Tried it (correct-mailbox.py) on a bigger part of my mail box and got:
libbe.util.graph.CyclicGraphError: 17 of 1000 elements not reachable from tips
--
Nicolas Pouillard
http://nicolaspouillard.fr
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2010-02-22 16:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 11:49 W. Trevor King
2010-02-21 6:38 ` Tero Tilus
2010-02-21 13:42 ` W. Trevor King
2010-02-21 17:52 ` Nicolas Pouillard
2010-02-21 19:29 ` W. Trevor King
2010-02-22 14:00 ` Nicolas Pouillard
2010-02-22 15:54 ` W. Trevor King
2010-02-22 16:04 ` Nicolas Pouillard [this message]
2010-02-22 16:48 ` W. Trevor King
2010-02-23 10:29 ` Nicolas Pouillard
2010-05-25 18:50 ` W. Trevor King
2010-06-03 4:27 ` Rich Lane
2010-06-03 10:21 ` W. Trevor King
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=4b82ab04.1067f10a.2460.ffffc8a4@mx.google.com \
--to=nicolas.pouillard@gmail.com \
--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