From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Lorenzo Bianconi <lorenzo@kernel.org>,
linux-iio <linux-iio@vger.kernel.org>,
"Lorenzo Bianconi" <lorenzo.bianconi@redhat.com>
Subject: Re: [PATCH] MAINTAINERS: updated Lorenzo's email address
Date: Wed, 30 Mar 2022 13:27:42 +0100 [thread overview]
Message-ID: <20220330132742.00005e12@Huawei.com> (raw)
In-Reply-To: <CAHp75VdpgB4xveRkmGAHEnYoEeiMUOL8J0NoovsXhuskwiwvtg@mail.gmail.com>
On Sun, 27 Mar 2022 22:38:49 +0300
Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
> On Sun, Mar 27, 2022 at 10:36 PM Jonathan Cameron <jic23@kernel.org> wrote:
> > On Thu, 24 Mar 2022 12:05:43 +0100
> > Lorenzo Bianconi <lorenzo@kernel.org> wrote:
> >
> > > Using my kernel.org email for iio devices.
>
> > Applied.
>
> I'm wondering all those email changes in the MAINTAINERS, are they
> being accompanied with the .mailcap changes?
> It would be good to have this done in order to decrease the amount of
> (email) bounces.
> OTOH dunno if get_maintainer.pl looks into .mailcap.
>
I'll guess, but in this case I think Lorenzo only wants to direct
mails about 'some' of the stuff he maintains to his kernel.org
account (as it's the stuff not related to the day job any more).
Hence for this one .mailmap change probably doesn't make sense.
Jonathan
prev parent reply other threads:[~2022-03-30 12:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 11:05 [PATCH] MAINTAINERS: updated Lorenzo's email address Lorenzo Bianconi
2022-03-27 14:35 ` Jonathan Cameron
2022-03-27 19:38 ` Andy Shevchenko
2022-03-30 12:27 ` Jonathan Cameron [this message]
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=20220330132742.00005e12@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=andy.shevchenko@gmail.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=lorenzo@kernel.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