From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-oa1-f43.google.com (mail-oa1-f43.google.com [209.85.160.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 57C673D6A for ; Sun, 2 Oct 2022 21:07:51 +0000 (UTC) Received: by mail-oa1-f43.google.com with SMTP id 586e51a60fabf-132555b7121so2099907fac.2 for ; Sun, 02 Oct 2022 14:07:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux-foundation.org; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=uJ9dwtxfZ7QDsWihPeAk/whJT6OEIJZ9L68Sp/smDb8=; b=fVw0+JqglxpVoZs6aXw9kNt0YWj70Gn920A8unExF66Z7OOFf4P8ITJU0n7X2HXTpl 5Y7YHBnpfYisZC7N0iVTAvORxzUCdZpTrkU545srbzIZQyYdbTBonec9WSLe1yj19kRE jehU7PYjG1eaq0/zPxMxklHdq1z9W/0nebmhM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=uJ9dwtxfZ7QDsWihPeAk/whJT6OEIJZ9L68Sp/smDb8=; b=XLc8tRmphBIXM6L8xfirqbCtkdtDgHGG4ofrHYoHz2spOHOGaf9EvLt2TVnZgPVoBP kSZgeNQ6W3Fhg1iAb9SWpCfrydxKBW+AkansCGTF2wKcUaFyKqGZHrFudfkWJMC9+6sJ oX1t/m8Y3PxxgGOkejZQQZQ7F/8iVFpJzrm9E/BV2FFU2he8m82tY4MNQGb2YTKv7dEw 8USWtPTmF9vOwuqebgBB0zpcCDbV9j/YfdHfn5gfMmHZethT/BrzwrMFygm2qSoplYZ2 ua2t5CKz4TgnAR27yossTy+OD8R5fVxJ7JQCAKoAyKMDrr1GsCGfwV0tVGB34ZOAFmD0 3S+w== X-Gm-Message-State: ACrzQf2USSKihZ00TBNWsrDOlOzwpXULiqrZkkKHktq/3jKbSEpwt5BZ t1gHZCgB2NnzJH5vBc6y6algaR6KX3wH2Q== X-Google-Smtp-Source: AMsMyM6NO2z+mTd080Jx9xKjxK+jGRkP/JYPBr6H5jEVFoIt0I7vP/z3h6vM2hgnd7HQFw7dor6lfA== X-Received: by 2002:a05:6870:a91f:b0:131:b7cc:fbaf with SMTP id eq31-20020a056870a91f00b00131b7ccfbafmr3789974oab.37.1664744869838; Sun, 02 Oct 2022 14:07:49 -0700 (PDT) Received: from mail-oa1-f42.google.com (mail-oa1-f42.google.com. [209.85.160.42]) by smtp.gmail.com with ESMTPSA id n64-20020acabd43000000b003502783c454sm2033199oif.0.2022.10.02.14.07.46 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 02 Oct 2022 14:07:46 -0700 (PDT) Received: by mail-oa1-f42.google.com with SMTP id 586e51a60fabf-131ea99262dso8801030fac.9 for ; Sun, 02 Oct 2022 14:07:46 -0700 (PDT) X-Received: by 2002:a05:6870:c0c9:b0:127:c4df:5b50 with SMTP id e9-20020a056870c0c900b00127c4df5b50mr3818161oad.126.1664744866051; Sun, 02 Oct 2022 14:07:46 -0700 (PDT) Precedence: bulk X-Mailing-List: ksummit@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 References: <9a2fdff8-d0d3-ebba-d344-3c1016237fe5@gmx.com> <83f6dd2b-784a-e6d3-ebaf-6ad9cfe4eefe@gmx.com> <79bb605a-dab8-972d-aa4a-a5e5ee49387c@gmx.com> <7d57b7d2-b39a-881c-65e6-969c4f0948cc@gmx.com> In-Reply-To: <7d57b7d2-b39a-881c-65e6-969c4f0948cc@gmx.com> From: Linus Torvalds Date: Sun, 2 Oct 2022 14:07:29 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Planned changes for bugzilla.kernel.org to reduce the "Bugzilla blues" To: "Artem S. Tashkinov" Cc: Greg KH , "Theodore Ts'o" , Thorsten Leemhuis , Konstantin Ryabitsev , workflows@vger.kernel.org, LKML , "regressions@lists.linux.dev" , ksummit@lists.linux.dev, Mario Limonciello Content-Type: text/plain; charset="UTF-8" On Sun, Oct 2, 2022 at 1:56 PM Artem S. Tashkinov wrote: > > I just want a bugzilla where I can CC _any_ developer _if_ and _only if_ > they are willing to work within its confounds. That's it. Guess what that "add develooper to the Cc" is called? Email. What you do is fill in the bugzilla entry with all the data you want. Then you use email to inform people about it. Put enough data in the email that the developer knows whether it's even worth looking at the bugzilla entry or not. Don't just put a link to the bugzilla. Most developers will just go "oh, this looks like spam"., Put the overview in the email, enough information that the developer can go "Ahh, this is worth my time", _and_ the link to bugzilla. That gives you exactly what you ask for: you can CC _any_ developer. And it doesn't force the developer to have to go to some bugzilla web interface unless the developer thinks it actually adds value. This is *literally* how I end up using bugzilla. As you say, I actually do end up looking at bugzilla entries in the end, but I only do it once it has hit my mailbox first, and I have some fairly good indication that it's worth my time to look at it. And yes, for some projects and for some developers you can do that email integration from within bugzilla itself. That's how people reach me. But this is exactly the kind of part of bugzilla that is a TOTAL HORROR-SHOW to manage, and it's impossible to expect every developer to be somebody that can be listed on bugzilla, without bugzilla becoming a prime way to send spam. Which is why in the general case, you really should consider email to be the "lingua franca" of kernel development communication. It doesn't have the fundamental limitations and management issues that bugzilla has. If you want to add more people to the Cc in an email, you just do it. Linus