From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 4AA50DB6 for ; Thu, 4 Jul 2019 14:16:13 +0000 (UTC) Received: from Galois.linutronix.de (Galois.linutronix.de [193.142.43.55]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 6A31E88E for ; Thu, 4 Jul 2019 14:16:12 +0000 (UTC) Date: Thu, 4 Jul 2019 16:16:03 +0200 (CEST) From: Thomas Gleixner To: Geert Uytterhoeven In-Reply-To: Message-ID: References: <7b73e1b7-cc34-982d-2a9c-acf62b88da16@linuxfoundation.org> <20190628205102.GA3131@agluck-desk2.amr.corp.intel.com> <87y31eov1l.fsf@concordia.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Cc: ksummit Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Patch version changes in commit logs? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thu, 4 Jul 2019, Geert Uytterhoeven wrote: > On Thu, Jul 4, 2019 at 2:22 PM Michael Ellerman wrote: > > If you've got the link back to the mailing list archive, do you also > > need Cc: tags in the change log? Probably not. > > It's always seemed to me they don't really add any value, they just tell > > you that lots of people were Cc'ed on the patch and probably didn't have > > time to review it :) > > +1 > > Especially if the CC list was generated by blindly copying the output > from scripts/get_maintainer.pl, without passing through a common sense > filter. And the maintainer then blindly picks it up :)