linux-kernel - RE: [2.6 patch] Tigran Aivazian: remove bouncing email addresses

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <00e901c71513$5f8397d0$6721100a@nuitysystems.com>
Date:	Thu, 30 Nov 2006 22:38:43 -0800
From:	"Hua Zhong" <hzhong@...il.com>
To:	"'Adrian Bunk'" <bunk@...sta.de>
Cc:	<tigran@...azian.fsnet.co.uk>, <linux-kernel@...r.kernel.org>
Subject: RE: [2.6 patch] Tigran Aivazian: remove bouncing email addresses

> 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@....com>
+ *	1.0	16 Feb 2000, Tigran Aivazian
  *		Initial release.
- *	1.01	18 Feb 2000, Tigran Aivazian <tigran@....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.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/