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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 11 Apr 2019 22:07:32 +1000
From:   Michael Ellerman <>
To:     Joe Perches <>,
        Lukas Bulwahn <>,
        Tyrel Datwyler <>
Cc:     "Paul E . McKenney" <>,,,, Josh Boyer <>
Subject: Re: [PATCH] MAINTAINERS: Update remaining addresses

Joe Perches <> writes:
> On Thu, 2019-04-11 at 06:27 +0200, Lukas Bulwahn wrote:
>> Paul McKenney attempted to update all email addresses
>> to in commit 1dfddcdb95c4
>> ("MAINTAINERS: Update from to"), but
>> some still remained.
>> We update the remaining email addresses in MAINTAINERS, hopefully finally
>> catching all cases for good.
> Perhaps update all the similar addresses in other files too
> $ git grep --name-only 'linux\.vnet\.ibm\.com' | wc -l
> 315

A good number of them are no longer valid. So I'm not sure it's worth
updating them en masse to addresses that won't ever work.

We have git now, we don't need email addresses in files, they're just
prone to bitrot like this.

Should we just change them all like so?

  -arch/powerpc/boot/dts/bamboo.dts: * Josh Boyer <>
  +arch/powerpc/boot/dts/bamboo.dts: * Josh Boyer (IBM)

To indicate the author was at IBM when they wrote it?

Or should we try and update them with current addresses? Though then the
authors might start getting mails they don't want.


Powered by blists - more mailing lists