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: Thu, 3 Jun 2010 06:21:10 -0400 [thread overview]
Message-ID: <20100603102109.GA1499@thialfi> (raw)
In-Reply-To: <1275538158-sup-1305@zyrg.net>
[-- Attachment #1.1.1: Type: text/plain, Size: 1661 bytes --]
On Thu, Jun 03, 2010 at 12:27:04AM -0400, Rich Lane wrote:
> I'm not yet convinced that supporting multiple parents is worth
> the complexity. How often do you get mails like this?
I don't get mails with multiple in-reply-tos, but I send them ;). I
*do* get mails with in-text references to multiple messages. For some
mailing lists that I care about (be-devel), I go through and adjust
in-reply-to so that it matches the in-text references.
I think such graphs would be a nice interface to mailing lists, which
gain members not familiar with the lists history. Browsing a curated
list, finding the critical background for a particular message would
be trivial.
> What mail clients have UI for replying to multiple messages?
In Mutt, you can tag a bunch of messages, and then ;g to reply-to-all
the tagged messages at once. I started doing this to get the previous
text from all the messages included in my reply, so I expect this sort
of thing does occur occasionally in the wild.
> I'd have to fake up some messages to actually see the full DAG
> support in action, so could you post a screenshot of your code
> viewing a thread where the new display helps?
Attached is a small graph showing two related threads about
bzr+windows. The multiparent replies allow responses like Matt's,
"we discussed this last year" message.
--
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.1.2: graph-threading.png --]
[-- Type: image/png, Size: 13150 bytes --]
[-- 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
prev parent reply other threads:[~2010-06-03 10:31 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
2010-06-03 4:27 ` Rich Lane
2010-06-03 10:21 ` W. Trevor King [this message]
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=20100603102109.GA1499@thialfi \
--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