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 0C9C6C433FE for ; Thu, 3 Dec 2020 19:25:30 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id B8C7122203 for ; Thu, 3 Dec 2020 19:25:29 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731107AbgLCTZ1 (ORCPT ); Thu, 3 Dec 2020 14:25:27 -0500 Received: from smtprelay0184.hostedemail.com ([216.40.44.184]:48560 "EHLO smtprelay.hostedemail.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726438AbgLCTZ0 (ORCPT ); Thu, 3 Dec 2020 14:25:26 -0500 Received: from filter.hostedemail.com (clb03-v110.bra.tucows.net [216.40.38.60]) by smtprelay01.hostedemail.com (Postfix) with ESMTP id 65A38100E7B44; Thu, 3 Dec 2020 19:24:45 +0000 (UTC) X-Session-Marker: 6A6F6540706572636865732E636F6D X-HE-Tag: lake02_0209186273be X-Filterd-Recvd-Size: 3285 Received: from XPS-9350.home (unknown [47.151.137.21]) (Authenticated sender: joe@perches.com) by omf12.hostedemail.com (Postfix) with ESMTPA; Thu, 3 Dec 2020 19:24:44 +0000 (UTC) Message-ID: <46efd4f2168b58c0da45c08b120a1b3deef9e169.camel@perches.com> Subject: Re: [Ksummit-discuss] crediting bug reports and fixes folded into original patch From: Joe Perches To: Konstantin Ryabitsev Cc: James Bottomley , Vlastimil Babka , "ksummit-discuss@lists.linuxfoundation.org" , LKML Date: Thu, 03 Dec 2020 11:24:43 -0800 In-Reply-To: <20201203191731.bpzvwqfldhcjhzfy@chatter.i7.local> References: <694039d6e386d999fd74d038cf2627f5b3b0ca71.camel@HansenPartnership.com> <3c11134905f06185dda4e9125f2fb7fd30fff979.camel@perches.com> <20201203191731.bpzvwqfldhcjhzfy@chatter.i7.local> Content-Type: text/plain; charset="ISO-8859-1" User-Agent: Evolution 3.38.1-1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2020-12-03 at 14:17 -0500, Konstantin Ryabitsev wrote: > On Thu, Dec 03, 2020 at 08:55:54AM -0800, Joe Perches wrote: > > Perhaps automate a mechanism to capture that information as > > git notes for the patches when applied. > > Git notes have a limited usefulness for this -- they are indeed part of > the repository, but they aren't replicated unless someone does a > --mirror clone (or specifically fetches refs/notes/*). If the goal is to > improve visibility for contributors, then putting this info into a git > note will hardly make more difference than providing a Link: that > someone has to follow to a list archival service. Or it becomes standard to fetch the refs/notes/... at the pull time. > I can offer the following proposal: > > - kernel.org already monitors all mailing lists that are archived on >   lore.kernel.org for the purposes of pull request tracking >   (pr-tracker-bot). > - in the near future, we will add a separate process that will >   auto-explode all pull requests into individual patches and add them >   to a separate public-inbox archive (think of it as another >   transparency log, since pull requests are transient and opaque). > > We can additionally: > > - identify all Link: and Message-Id: entries in commit messages, >   retrieve the threads they refer to, and archive them as part of the >   same (or adjacent) transparency log. > > This offers an improvement over the status quo, because if > lore.kernel.org becomes unavailable, someone would have to have access > to all backend archive repositories it is currently tracking in order to > be able to reconstitute relevant conversations -- whereas with this > change, it should be sufficient to just have the copy of the > transparency log to have a fully self-contained high-relevancy archive > of both individual commits and conversations that happened around them. I think that would be great. Thanks. I think all the requests for additional -by: -from: signature/bylines becoe unnecessary if and when this proposal is implemented.