From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from wp530.webpack.hosteurope.de (wp530.webpack.hosteurope.de [80.237.130.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 46EED20F7; Tue, 4 Oct 2022 07:37:37 +0000 (UTC) Received: from [2a02:8108:963f:de38:eca4:7d19:f9a2:22c5]; authenticated by wp530.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1ofcUc-0005WV-IW; Tue, 04 Oct 2022 09:37:30 +0200 Message-ID: <109147a2-621d-d4ce-f4b3-8516664e138e@leemhuis.info> Date: Tue, 4 Oct 2022 09:37:29 +0200 Precedence: bulk X-Mailing-List: ksummit@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.3.1 Content-Language: en-US, de-DE To: Konstantin Ryabitsev , Mike Rapoport Cc: "Artem S. Tashkinov" , Al Viro , Steven Rostedt , Theodore Ts'o , Greg KH , workflows@vger.kernel.org, LKML , Linus Torvalds , "regressions@lists.linux.dev" , ksummit@lists.linux.dev, Mario Limonciello References: <79bb605a-dab8-972d-aa4a-a5e5ee49387c@gmx.com> <20221002141321.394de676@rorschach.local.home> <6de0925c-a98a-219e-eed2-ba898ef974f8@gmx.com> <20221002180844.2e91b1f1@rorschach.local.home> <3a3b9346-e243-e178-f8dd-f8e1eacdc6ae@gmx.com> <20221003153718.o7fhrain5fnwwu3l@meerkat.local> From: Thorsten Leemhuis Subject: Re: Planned changes for bugzilla.kernel.org to reduce the "Bugzilla blues" In-Reply-To: <20221003153718.o7fhrain5fnwwu3l@meerkat.local> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-bounce-key: webpack.hosteurope.de;linux@leemhuis.info;1664869057;401b708d; X-HE-SMSGID: 1ofcUc-0005WV-IW On 03.10.22 17:37, Konstantin Ryabitsev wrote: > > If we auto-create accounts for MAINTAINERS, that would allow them to be cc'd > by an actual human being triaging bugs, [...] For the record: that would not be enough, as for bisected regressions you often want to CC the author of the culprit who might not be a maintainer. To catch that case as well, you'd have to create account for everyone that contributes a change. Ciao, Thorsten