mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Shuah Khan <skhan@linuxfoundation.org>,
	mchehab+huawei@kernel.org, davem@davemloft.net, robh@kernel.org,
	gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Update my maintainer entries to reorder email addresses
Date: Tue, 26 May 2020 16:33:09 -0700	[thread overview]
Message-ID: <fd6892ca0191b67491416318958d1ece23e840ff.camel@perches.com> (raw)
In-Reply-To: <ea204501-84a3-badb-63f6-0a9d2fe12b19@linuxfoundation.org>

On Tue, 2020-05-26 at 16:54 -0600, Shuah Khan wrote:
> On 5/26/20 4:27 PM, Joe Perches wrote:
> > On Tue, 2020-05-26 at 11:04 -0600, Shuah Khan wrote:
> > > On 5/22/20 8:26 PM, Joe Perches wrote:
> > > > On Fri, 2020-05-22 at 20:19 -0600, Shuah Khan wrote:
> > > > > get_maintainer.pl picks only the first email address found in the file.
> > > > > Reorder my email addresses so it finds my linuxfoundation.org email.
> > > > 
> > > > OK.
> > []
> > > Sadly, people that don't run get_maintainer.pl, leave alone running it
> > > with --noremove-duplicates option. So your suggestion doesn't really
> > > help me.
> > > 
> > > My preference is to get patches to both Inboxes if possible which isn't
> > > possible unless -noremove-duplicate is default. Having this option as
> > > default probably will annoy lot of people . So I am not asking for
> > > that.
> > > 
> > > That being said, I don't understand your comment. Are you recommending
> > > using just one email in these entries?
> > 
> > Yes.  And maybe set an autoforward rule in that email to
> > forward the received email to your other address.
> > 
> > 
> Sounds good.

Another option would be to write your name
slightly differently in the 2 entries.

For instance, add "(LF)" to the linuxfoundation.org entry like:

CPU POWER MONITORING SUBSYSTEM
M:	Thomas Renninger <trenn@suse.com>
M:	Shuah Khan <shuah@kernel.org>
M:	Shuah Khan (LF) <skhan@linuxfoundation.org>
L:	linux-pm@vger.kernel.org
S:	Maintained
F:	tools/power/cpupower/

and then the get_maintainer.pl script won't
collapse the equally named but with different
email addresses into a single entry:

$ ./scripts/get_maintainer.pl -f tools/power/cpupower/
Thomas Renninger <trenn@suse.com> (maintainer:CPU POWER MONITORING SUBSYSTEM)
Shuah Khan <shuah@kernel.org> (maintainer:CPU POWER MONITORING SUBSYSTEM)
"Shuah Khan (LF)" <skhan@linuxfoundation.org> (maintainer:CPU POWER MONITORING SUBSYSTEM)
linux-pm@vger.kernel.org (open list:CPU POWER MONITORING SUBSYSTEM)
linux-kernel@vger.kernel.org (open list)




  reply	other threads:[~2020-05-26 23:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-23  2:19 Shuah Khan
2020-05-23  2:26 ` Joe Perches
2020-05-26 17:04   ` Shuah Khan
2020-05-26 22:27     ` Joe Perches
2020-05-26 22:54       ` Shuah Khan
2020-05-26 23:33         ` Joe Perches [this message]
2020-05-26 23:40           ` Shuah Khan
2020-05-23  5:57 ` Mauro Carvalho Chehab
2020-05-23  6:14   ` Joe Perches

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=fd6892ca0191b67491416318958d1ece23e840ff.camel@perches.com \
    --to=joe@perches.com \
    --cc=davem@davemloft.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=robh@kernel.org \
    --cc=skhan@linuxfoundation.org \
    /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

all inboxes | Powered by JetHome®