From: Michael Ellerman <mpe@ellerman.id.au>
To: Joe Perches <joe@perches.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Tyrel Datwyler <tyreld@linux.ibm.com>
Cc: "Paul E . McKenney" <paulmck@linux.ibm.com>,
linux-pci@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, Josh Boyer <jwboyer@kernel.org>
Subject: Re: [PATCH] MAINTAINERS: Update remaining @linux.vnet.ibm.com addresses
Date: Thu, 11 Apr 2019 22:07:32 +1000 [thread overview]
Message-ID: <87k1g0vj7f.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <0702bc9a10703d53a46f27468b2c9ef2463e1c0b.camel@perches.com>
Joe Perches <joe@perches.com> writes:
> On Thu, 2019-04-11 at 06:27 +0200, Lukas Bulwahn wrote:
>> Paul McKenney attempted to update all email addresses @linux.vnet.ibm.com
>> to @linux.ibm.com in commit 1dfddcdb95c4
>> ("MAINTAINERS: Update from @linux.vnet.ibm.com to @linux.ibm.com"), 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 <jwboyer@linux.vnet.ibm.com>
+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.
cheers
next prev parent reply other threads:[~2019-04-11 12:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 4:27 [PATCH] MAINTAINERS: Update remaining @linux.vnet.ibm.com addresses Lukas Bulwahn
2019-04-11 11:33 ` Paul E. McKenney
2019-04-11 11:45 ` Joe Perches
2019-04-11 12:07 ` Michael Ellerman [this message]
2019-04-11 12:27 ` Joe Perches
2019-04-11 13:12 ` Paul E. McKenney
2019-04-12 16:16 ` Joe Perches
2019-04-21 14:19 ` Michael Ellerman
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=87k1g0vj7f.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=joe@perches.com \
--cc=jwboyer@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lukas.bulwahn@gmail.com \
--cc=paulmck@linux.ibm.com \
--cc=tyreld@linux.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).