From: Gaute Hope <eg@gaute.vetsj.com>
To: Michael Stapelberg <michael+sup@stapelberg.de>
Cc: Sup developer discussion <sup-devel@rubyforge.org>,
Rich Lane <rlane@club.cc.cmu.edu>
Subject: Re: [sup-devel] [PATCH] Bugfix: Don’t display thread participants twice
Date: Fri, 8 Oct 2010 13:46:28 +0200 [thread overview]
Message-ID: <AANLkTi=ezGsXB7jHtSV1+9fREThpvPERZEOjm8TpXcVA@mail.gmail.com> (raw)
In-Reply-To: <1286538002-sup-2671@midna.zekjur.net>
On Fri, Oct 8, 2010 at 1:41 PM, Michael Stapelberg
<michael+sup@stapelberg.de> wrote:
> Hi Gaute,
>
> Excerpts from Gaute Hope's message of 2010-10-08 12:05:29 +0200:
>> What if someone has the same name ? ;) Is it more
>> important/likely/intuitive than anyone using two addresses?
> If two people have exactly the same name, you would not benefit in seeing that
> same name twice, either. Even if one mail of the thread is new and one "Michael
> S." is highlighted, you still would not know which one sent the new mail. So,
> to avoid confusion about the same name showing up twice, I decided it would be
> better to not show duplicates at all.
Sure, this isn't really a big issue (for me at least). The duplicates
would be the expected behaviour (for me :)), the benefit being that
you know there is one more guy/emailaccount at work here.
Best regards, Gaute
next prev parent reply other threads:[~2010-10-08 11:46 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 [this message]
2010-10-08 12:07 ` Ben Walton
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='AANLkTi=ezGsXB7jHtSV1+9fREThpvPERZEOjm8TpXcVA@mail.gmail.com' \
--to=eg@gaute.vetsj.com \
--cc=michael+sup@stapelberg.de \
--cc=rlane@club.cc.cmu.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