Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp4468554pxf; Tue, 23 Mar 2021 11:17:27 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy9gZDa+ZyYoQ7n2LVL5SRByEht5wqCNbPREichOqmez4IT2W+rYlY93pVJjjbFzppcGPBb X-Received: by 2002:a17:906:f0c8:: with SMTP id dk8mr6274907ejb.300.1616523446801; Tue, 23 Mar 2021 11:17:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1616523446; cv=none; d=google.com; s=arc-20160816; b=gh1kRiuROvJUwaBynTrWjcdl0LL2ovFy2UF2bEiBEexIlVvdagwAwAYjFjgPIbGxEp Y+fz1zKAKWBYkNr81w22IAcoAttnF8h+NLfeCPz98ow1F96FOdC9mjJFBhQpQbPeJVTT ZfZJs89p0KWxYsqpMPi8a/v9mLz/q4nBvoQaek6ciHxdHPFOU3QSsgteBWJBJVwDfaOd +DxTnThdm4kY+GQLSWji2YKLPYbb+RPnHgigs5Suh/B7/lZTHc+1VZd/zsTryTczY6Wt ILAf96uKLUlYdW6CBu77GwKeGT3E6hFD4Y5xsY1XNZQMqk523RLbRacn5YsoAf3o6/tL LOdA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=lwarh8YCcmK+WEXahvJbB9eWFkG8P850/6mkValF/rQ=; b=qrNBDRUQCLA+S2ro3odAQzB98loM9ZNa+TOQwVWHNN/67FRHla3hup5AxPwFhojyck LL4dfBlk7HiRvBd+oM9iVSdOOdq8OR+F55l7VRVV/v/y9B+nkf8hIwe7w0P8gl21yts+ AqXa5HX/vWkTOjma3txGn1eSw4nPqRq55Uvt0D3j1BErX++ST+IQmiezsyGmKvsm0mpQ P7AGt8AgOYxfEB8yP08sHxNXHPFZEF9cS/qJ020KpkY5EA9iaOe7yzW7ihht3rSrITf5 VMvsb2dehNVWHQ6ekH+5dfovb0V32h1+oQanTksXQNthQYI1q8mLFsJVI2UHEi2HA5Jw hYGg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id y23si13481603eds.278.2021.03.23.11.17.03; Tue, 23 Mar 2021 11:17:26 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231233AbhCWSMU (ORCPT + 99 others); Tue, 23 Mar 2021 14:12:20 -0400 Received: from outgoing-auth-1.mit.edu ([18.9.28.11]:56154 "EHLO outgoing.mit.edu" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S231214AbhCWSMC (ORCPT ); Tue, 23 Mar 2021 14:12:02 -0400 Received: from cwcc.thunk.org (pool-72-74-133-215.bstnma.fios.verizon.net [72.74.133.215]) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 12NIBs7r012557 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 23 Mar 2021 14:11:55 -0400 Received: by cwcc.thunk.org (Postfix, from userid 15806) id 6FBA415C39CC; Tue, 23 Mar 2021 14:11:54 -0400 (EDT) Date: Tue, 23 Mar 2021 14:11:54 -0400 From: "Theodore Ts'o" To: Thorsten Leemhuis Cc: Linus Torvalds , Konstantin Ryabitsev , Greg KH , workflows@vger.kernel.org, Linux Kernel Mailing List , ksummit Subject: Re: [Ksummit-discuss] RFC: create mailing list "linux-issues" focussed on issues/bugs and regressions Message-ID: References: <613fe50d-fc9c-6282-f1f3-34653acb2ee9@leemhuis.info> <62b60247-7838-a624-706e-b1a54785b2a5@leemhuis.info> <54aeb1f7-ffc7-74e1-a731-8970d44ff852@leemhuis.info> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <54aeb1f7-ffc7-74e1-a731-8970d44ff852@leemhuis.info> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Mar 23, 2021 at 09:57:57AM +0100, Thorsten Leemhuis wrote: > On 22.03.21 22:56, Theodore Ts'o wrote: > > On Mon, Mar 22, 2021 at 08:25:15PM +0100, Thorsten Leemhuis wrote: > >> I agree to the last point and yeah, maybe regressions are the more > >> important problem we should work on – at least from the perspective of > >> kernel development. But from the users perspective (and > >> reporting-issues.rst is written for that perspective) it feel a bit > >> unsatisfying to not have a solution to query for existing report, > >> regressions or not. Hmmmm... > > First of all, thanks for working on reporting-issues.rst. > > Thx, very glad to hear that. I didn't get much feedback on it, which > made me wonder if anybody besides docs folks actually looked at it... I'll admit that I had missed your initial submission, but having looked at it, while I could imagine some nits where it could be improved, in my opinion, it's strictly better than the older reporting-bugs doc. > Hmmm, yeah, I like that idea. I'll keep it in mind for later: I would > prefer to get reporting-issues.rst officially blessed and > reporting-bugs.rst gone before working on further enhancements. Is there anyone following this thread who believes that there is anything we should change *before* oficially blessing reporting-issues.rst? Given that Konstantin has already linked to reporting-issues from the front page of kernel.bugzilla.org, I think we we should just go ahead and officially bless it and be done with it. :-) Once it is blessed, I'd also suggest putting a link to https://www.kernel.org/doc/html/latest/admin-guide/reporting-issues.html as an "other resources" at https://www.kernel.org. - Ted