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: <Pine.LNX.4.61.0612010919170.29499@ginsburg.homenet>
Date:	Fri, 1 Dec 2006 09:21:36 +0000 (GMT)
From:	Tigran Aivazian <tigran@...azian.fsnet.co.uk>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	Hua Zhong <hzhong@...il.com>, 'Adrian Bunk' <bunk@...sta.de>,
	linux-kernel@...r.kernel.org
Subject: RE: [2.6 patch] Tigran Aivazian: remove bouncing email addresses

Hi Arjan,

On Fri, 1 Dec 2006, Arjan van de Ven wrote:

> On Thu, 2006-11-30 at 22:00 -0800, Hua Zhong 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.
>
>
> .. and which company owns the copyright.

VERITAS doesn't own any copyright of the microcode driver because I wrote 
it _before_ I joined VERITAS.

> Lets not remove historical email addresses. Just make sure there's a
> current one in MODULE_AUTHOR / MAINTAINERS.

I agree, so I should have included in the patch the change to 
MODULE_AUTHOR (in both microcode and bfs).

Or maybe MODULE_AUTHOR shouldn't contain the email address, if the module 
is mentioned in the MAINTAINERS which does contain it? Why repeat the data 
and so have to remember to maintain it?

Kind regards
Tigran
-
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/