From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] question about contacts
Date: Mon, 05 May 2008 18:02:20 -0700 [thread overview]
Message-ID: <1210035671-sup-1419@south> (raw)
In-Reply-To: <1209564726-sup-7788@h984274.serverkompetenz.net>
Reformatted excerpts from Tyberius Prime's message of 2008-04-30:
> But I'm also interested behind the rationale to "unify" sender names
> like that (maybe there's a good reason that the both of us are
> missing)!
No, there was no good reason. I thought it was clever but didn't realize
what the consequences would be when I did it. I think things are now in
a state where removing all that stuff wouldn't be too hard, and I've
been meaning to do it for quite some time, just haven't gotten around to
it.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2008-05-06 1:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 0:07 Ben Walton
2008-04-30 14:12 ` Tyberius Prime
2008-05-06 1:02 ` William Morgan [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=1210035671-sup-1419@south \
--to=wmorgan-sup@masanjin.net \
/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