From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3CFC8C433FE for ; Thu, 3 Dec 2020 16:56:55 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id D29BC207A5 for ; Thu, 3 Dec 2020 16:56:54 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2436614AbgLCQ4i (ORCPT ); Thu, 3 Dec 2020 11:56:38 -0500 Received: from smtprelay0086.hostedemail.com ([216.40.44.86]:33996 "EHLO smtprelay.hostedemail.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725999AbgLCQ4i (ORCPT ); Thu, 3 Dec 2020 11:56:38 -0500 Received: from filter.hostedemail.com (clb03-v110.bra.tucows.net [216.40.38.60]) by smtprelay06.hostedemail.com (Postfix) with ESMTP id 35ED118224D60; Thu, 3 Dec 2020 16:55:57 +0000 (UTC) X-Session-Marker: 6A6F6540706572636865732E636F6D X-HE-Tag: grain99_2c007c7273bd X-Filterd-Recvd-Size: 2150 Received: from XPS-9350.home (unknown [47.151.137.21]) (Authenticated sender: joe@perches.com) by omf15.hostedemail.com (Postfix) with ESMTPA; Thu, 3 Dec 2020 16:55:56 +0000 (UTC) Message-ID: <3c11134905f06185dda4e9125f2fb7fd30fff979.camel@perches.com> Subject: Re: [Ksummit-discuss] crediting bug reports and fixes folded into original patch From: Joe Perches To: James Bottomley , Vlastimil Babka , "ksummit-discuss@lists.linuxfoundation.org" Cc: LKML Date: Thu, 03 Dec 2020 08:55:54 -0800 In-Reply-To: <694039d6e386d999fd74d038cf2627f5b3b0ca71.camel@HansenPartnership.com> References: <694039d6e386d999fd74d038cf2627f5b3b0ca71.camel@HansenPartnership.com> Content-Type: text/plain; charset="ISO-8859-1" User-Agent: Evolution 3.38.1-1 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2020-12-03 at 05:58 -0800, James Bottomley wrote: > So there are two embedded questions here: firstly, should we be as > wedded to clean history as we are, because showing the evolution would > simply solve this? Secondly, if we are agreed on clean history, how > can we make engagement via email as important as engagement via commit > for the community managers so the Link tag is enough? I've got to say > I think trying to add tags to recognize patch evolution is a mistake > and we instead investigate one of the two proposals above. I don't care that any trivial style notes I give to anyone are tracked for posterity. Who are these 'community managers' that use these? Signatures are a mechanism for credit tracking isn't great. One style that seems to have been generally accepted is for patch revision change logs to be noted below a --- line. Often that change log will shows various improvements made to a patch and the people and reasoning that helped make those improvements. Perhaps automate a mechanism to capture that information as git notes for the patches when applied.