From: Ben Walton <bwalton@artsci.utoronto.ca>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [PATCH] Bugfix: Don’t display thread participants twice
Date: Fri, 08 Oct 2010 08:07:32 -0400 [thread overview]
Message-ID: <1286539610-sup-1173@pinkfloyd.chass.utoronto.ca> (raw)
In-Reply-To: <AANLkTi=Ppaa6jA=pKOeLPEVhhqjvDg1-cS7QUsmZ+QYK@mail.gmail.com>
Excerpts from Gaute Hope's message of Fri Oct 08 06:05:29 -0400 2010:
> What if someone has the same name ? ;) Is it more
> important/likely/intuitive than anyone using two addresses?
A good point, but I'd still rather see a shorter list. The space is
limited, so squashing duplicate names is fine with me.
HTH.
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
prev parent reply other threads:[~2010-10-08 12:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 17:21 Michael Stapelberg
2010-10-08 4:17 ` Rich Lane
2010-10-08 10:05 ` Gaute Hope
2010-10-08 11:41 ` Michael Stapelberg
2010-10-08 11:46 ` Gaute Hope
2010-10-08 12:07 ` Ben Walton [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=1286539610-sup-1173@pinkfloyd.chass.utoronto.ca \
--to=bwalton@artsci.utoronto.ca \
--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