From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Hua Zhong" <hzhong@gmail.com>
Cc: "Adrian Bunk" <bunk@stusta.de>,
tigran@aivazian.fsnet.co.uk, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] Tigran Aivazian: remove bouncing email addresses
Date: Fri, 1 Dec 2006 22:40:43 +0100 [thread overview]
Message-ID: <9a8748490612011340w75199a6co91c233f71f4090f6@mail.gmail.com> (raw)
In-Reply-To: <00e401c7150e$061da500$6721100a@nuitysystems.com>
On 01/12/06, Hua Zhong <hzhong@gmail.com> wrote:
> I am curious, what's the point?
>
> These email addresses serve a "historical" purpose: they tell when the contribution was made, what the author's email addresses
> were at that point.
>
> It's not MAINTAINERS. If people want to contact someone, go find the latest address there.
>
Yes, MAINTAINERS is the preferred location for maintainer info, but
when there is no entry in maintainers (or when the person listed there
is not responsive), many people (including me) use the names or email
addresses listed in source files as people to contact. So it's nice
when the email addresses are up to date.
In my opinion the addresses should be working ones or not present at
all (or at the very least there should be a note that the email
address is outdated).
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2006-12-01 21:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-01 5:51 Adrian Bunk
2006-12-01 6:00 ` Hua Zhong
2006-12-01 6:19 ` Adrian Bunk
2006-12-01 6:38 ` Hua Zhong
2006-12-01 9:08 ` Arjan van de Ven
2006-12-01 9:21 ` Tigran Aivazian
2006-12-01 9:26 ` Arjan van de Ven
2006-12-01 10:59 ` Adrian Bunk
2006-12-02 21:08 ` Tigran Aivazian
2006-12-02 21:32 ` Adrian Bunk
2006-12-02 21:42 ` Alan
2006-12-02 22:07 ` grundig
2006-12-02 22:02 ` Tigran Aivazian
2006-12-01 20:33 ` Stephen Pollei
2006-12-01 21:40 ` Jesper Juhl [this message]
2006-12-02 21:33 ` Tigran Aivazian
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=9a8748490612011340w75199a6co91c233f71f4090f6@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=bunk@stusta.de \
--cc=hzhong@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tigran@aivazian.fsnet.co.uk \
/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
all inboxes | Powered by JetHome®