On Tue, Mar 22, 2022 at 11:19:50AM +0100, Krzysztof Kozlowski wrote: > On 21/03/2022 16:55, Greg KH wrote: > > On Mon, Mar 21, 2022 at 03:47:43PM +0100, Krzysztof Kozlowski wrote: > >> From: Krzysztof Kozlowski <krzysztof.kozlowski@xxxxxxxxxxxxx> > >> > >> commit 5125091d757a251a128ec38d2397c9d160394eac upstream. > >> > >> Use Krzysztof Kozlowski's @kernel.org account in maintainer entries. > >> > >> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@xxxxxxxxxxxxx> > >> Link: https://lore.kernel.org/r/20220307172805.156760-1-krzysztof.kozlowski@xxxxxxxxxxxxx' > >> Signed-off-by: Arnd Bergmann <arnd@xxxxxxxx> > >> --- > >> .mailmap | 1 + > >> MAINTAINERS | 28 ++++++++++++++-------------- > >> 2 files changed, 15 insertions(+), 14 deletions(-) > > > > We do not normally do MAINTAINERS updates for older kernel trees as no > > one should be doing development against them. > > > > Any reason why this is different? > > > > Hi Greg, > > No, it's not different, but people work on backports for stables on a > stable branch. Then they send such patch from within the stable tree, > because it's easier, I guess. Without the .mailmap all these backports > will go to wrong email address - my @canonical.com will start bouncing > in two days. > > In the same time I am not sure which mailmap is being followed by your > and other stable-folks tools, when notifying with backport queue > ("5.16.17-rc1 review" etc.). I don't use any tools that uses the mailmap file at all. So updating it isn't going to affect the stable patch review process, sorry. > Plus people actually might have some questions about some my backported > commit. They might respond to the email shown in git log, which will be > wrong without mailmap file. People change email addresses all the time, this isn't anything new. I really don't want to get into the habit of having to keep this file up to date with Linus's tree for 6 years, sorry. thanks, greg k-h