From: "W. Trevor King" <wking@drexel.edu>
To: Sup developer discussion <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] email threading - tree vs. graph
Date: Tue, 25 May 2010 14:50:27 -0400 [thread overview]
Message-ID: <20100525185026.GA11947@thialfi.home.net> (raw)
In-Reply-To: <1266730498-sup-78@tilus.net>
[-- Attachment #1.1: Type: text/plain, Size: 1571 bytes --]
On Sun, Feb 21, 2010 at 08:38:35AM +0200, Tero Tilus wrote:
> W. Trevor King, 2010-02-18 13:49:
> > Since email can have multiple parents [1], why does everyone make
> > threads trees rather than directed, acyclic graphs (DAGs)?
> > ...
> > On an implementation level, I've got the above graph browser going
> > in python/curses, so it should be easy to port to ruby/curses.
>
> Have a pointer to code?
>
> I would love to see sup being able to do something usefull with
> multiple parent messages.
I got some good feedback from Nicolas Pouillard on the Python tidbit I
posted, but after waiting optimisticly for some enterprising Rubist to
port it to Ruby and merge it into Sup, I've finally taught myself
enough Ruby to do it myself ;). Here's DAG-supporting Sup (+ a few
glaring documentation updates)
http://www.physics.drexel.edu/~wking/code/git/git.php?p=sup.git
I haven't done any benchmarking vs the tree-threading code, but if it
turns out to be too slow, we can always use:
if @graph_thread
...general...code...
else
...old...tree...code...
end
for bottleneck methods.
We could also resurect the old indentation-style display in the thread
viewer, if people dislike my tig-style ascii graph.
Cheers,
Trevor
--
This email may be signed or encrypted with GPG (http://www.gnupg.org).
The GPG signature (if present) will be attached as 'signature.asc'.
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
My public key is at http://www.physics.drexel.edu/~wking/pubkey.txt
[-- Attachment #1.2: Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2010-05-25 19:15 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
2010-02-22 16:48 ` W. Trevor King
2010-02-23 10:29 ` Nicolas Pouillard
2010-05-25 18:50 ` W. Trevor King [this message]
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=20100525185026.GA11947@thialfi.home.net \
--to=wking@drexel.edu \
--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