public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Hua Zhong" <hzhong@gmail.com>
To: "'Adrian Bunk'" <bunk@stusta.de>
Cc: <tigran@aivazian.fsnet.co.uk>, <linux-kernel@vger.kernel.org>
Subject: RE: [2.6 patch] Tigran Aivazian: remove bouncing email addresses
Date: Thu, 30 Nov 2006 22:38:43 -0800	[thread overview]
Message-ID: <00e901c71513$5f8397d0$6721100a@nuitysystems.com> (raw)
In-Reply-To: <20061201061958.GL11084@stusta.de>

> On Thu, Nov 30, 2006 at 10:00:35PM -0800, Hua Zhong wrote:
> 
> > I am curious, what's the point?
> 
> Email addresses are for contacting people.

Do you go back and change all the signed-off lines too when people change jobs?
 
> > These email addresses serve a "historical" purpose: they tell
> > when the contribution was made,  what the author's email addresses 
> > were at that point.
> 
> For historical purposes, you can always use historical kernels.

Then remove all the lines like the following:

- *	1.0	16 Feb 2000, Tigran Aivazian <tigran@sco.com>
+ *	1.0	16 Feb 2000, Tigran Aivazian
  *		Initial release.
- *	1.01	18 Feb 2000, Tigran Aivazian <tigran@sco.com>
+ *	1.01	18 Feb 2000, Tigran Aivazian 
  *		Added read() support + cleanups.

If you keep them, they tell the history and email addresses are part of the history.

Or simply remove all the history and tell people to look for the information in git changelogs.

The way you are doing it, serves no purpose other than losing information.

> > It's not MAINTAINERS. If people want to contact someone, go 
> > find the latest address there.
> 
> It's also MODULE_AUTHOR() and printk() which are far more 
> user-visible than MAINTAINERS.

Those are OK. But majority of you patch isn't the case.


  reply	other threads:[~2006-12-01  6:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-01  5:51 [2.6 patch] Tigran Aivazian: remove bouncing email addresses Adrian Bunk
2006-12-01  6:00 ` Hua Zhong
2006-12-01  6:19   ` Adrian Bunk
2006-12-01  6:38     ` Hua Zhong [this message]
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
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='00e901c71513$5f8397d0$6721100a@nuitysystems.com' \
    --to=hzhong@gmail.com \
    --cc=bunk@stusta.de \
    --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