Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp3774956pxf; Mon, 22 Mar 2021 15:00:58 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz9M7ktbKzpIB4oMIjFEX9o8fdwLacdHxA5vqAEyd+3kGYBHSf7AqIZm8WJg4lAnpVB/yA9 X-Received: by 2002:a17:906:4b0e:: with SMTP id y14mr1732220eju.393.1616450458373; Mon, 22 Mar 2021 15:00:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1616450458; cv=none; d=google.com; s=arc-20160816; b=cIwDgnneWzBKb7k6kdzlZ+doe97NfPPeZu1AiY5I9vhD94oi/8SX0RRUc9ne4vPpUd 1IZFyL8etAPcJBnY997eSuypsj4Q3ENQA1SYgk6p18EOvIPP1On9nbS7zjgv+qFjhHrP Y3zNCWKe+TezrRhV2QU7AX50usQWopGuFjCsSSHoRfki9aXJv2frG0whtP6lFOcV1v28 ROkRaKwBkYUhNj2cqC3TC2SV/S7VkXETx7TzlwCn3YY9glHYegs9xLHk6lCSy8tGwD+y NPOQAJawWi9e1CntCADJpeRDBVPnZhYwqHubwuCWUSmn9Qr1msycHuPQMYGLLud0etdz u+hQ== 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=BmgtwFJqSbIFaTtrY+mKlIEoWjK6WvXTyNa7TIBySGk=; b=hw/V1stG5+8TP+GWED0wnduK2mgTnja7wThntwp44YmE18K5jQJTaFhU/eulLL43Wq OHCO/wMzoH2+5zZihwDzg4V8qdB7vVyJkP2i/Rac8YUjW89ec0vfBlxComBWQ2Evtw6w 0TtnXiq1Bsa6osvruuH0WzundmVEVE1d9Z7Y7Nv5G9RaTRnM/PEaJg7rkveNd9cYcuTL 2ndnyXmsrcZ/U+PUcSH6WBuPS5ntbuw355ZvxCVO0t+nl/Z2xZKm8Dq0cDVZ+jtrhyDd bXzEZTeMfxS9SDLdaa8zta7EfY2NMOK2C+BVnPGFniYyDmrDKqBNyxn6Ce7UR4Dezsxo PpvQ== 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 h25si12642215eje.653.2021.03.22.15.00.34; Mon, 22 Mar 2021 15:00:58 -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 S230194AbhCVV5h (ORCPT + 99 others); Mon, 22 Mar 2021 17:57:37 -0400 Received: from outgoing-auth-1.mit.edu ([18.9.28.11]:56150 "EHLO outgoing.mit.edu" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S229730AbhCVV5J (ORCPT ); Mon, 22 Mar 2021 17:57:09 -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 12MLuuMT020632 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 22 Mar 2021 17:56:57 -0400 Received: by cwcc.thunk.org (Postfix, from userid 15806) id 754A315C39CC; Mon, 22 Mar 2021 17:56:56 -0400 (EDT) Date: Mon, 22 Mar 2021 17:56:56 -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> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <62b60247-7838-a624-706e-b1a54785b2a5@leemhuis.info> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. If we can actually get users to *read* it, I think it's going to save kernel developers a huge amount of time and frustration. I wonder if it might be useful to have a form which users could be encouraged to fill out so that (a) the information is available in a structured format so it's easier for developers to find the relevant information, (b) so it is easier for programs to parse, for easier reporting or indexing, and (c) as a nudge so that users remember to report critical bits of information such as the hardware configuration, the exact kernel version, which distribution userspace was in use, etc. There could also be something in the text form which would make it easier for lore.kernel.org searches to identify bug reports. (e.g., "LINUX KERNEL BUG REPORTER TEMPLATE") - Ted