Received: by 2002:a05:6a10:16a7:0:0:0:0 with SMTP id gp39csp1606519pxb; Fri, 20 Nov 2020 14:01:12 -0800 (PST) X-Google-Smtp-Source: ABdhPJxR+hEaytVmysWTZz4pSgmkeKjnCC5lK1lZy+qqQDn+Vnnw3BUIgD3mL3YtLc0j1BJq3215 X-Received: by 2002:a50:a105:: with SMTP id 5mr36380884edj.165.1605909672290; Fri, 20 Nov 2020 14:01:12 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1605909672; cv=none; d=google.com; s=arc-20160816; b=bm9+ME5sI9EIMMAM9zg+7jZEXNSPopzH/t1Tl0tuFQ8k+ZIRXU+e3sEBiMF9jhbOIc 33TzUpMZiUmDQoljt9PO6M6wMUFirkgQNkbOPJiffsq966eMHpy+w9BlOnfxRAt6K7jn LByGAvbUU+/Uk93EnN+haQS7lqjSWfIFUuqm/IyWORCey3gesofSE3kR3LSeJwy+kp3U 0x78UofNWrBscoH8aF4KQENGYMhGe0zDv829ldzRI5qQxIr7Y1tLBTwYa65T4YmCfMsj cYZMipd/hwCmrEiuOlNNwAMIfJb7U1dLFhBpxq15LrObH2K7EGDcNH0GvUpT0eawGM9j 3/cA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date; bh=n9yoCAHlAmLrHeGFzXx3DDdd1yfz4rRhxlAkhQ1vm8Y=; b=PKWnoUAp+f8N20rT+pkir9ub9wYatshO2pwd4ehUWl0HywIybaNpWw4E6xG3EkdhWe Szpi4wWId+mYkPaOh3/vH5IrfcgxG1kj55moovoZCEbZ7Jig50y4xfc5Zpcjr/1PTn0v JFZKeDl2dhM74zwC7eVlzw9NHa/0desq1Yv7c1LTGtRR+waNsD2NGlxmKQ55cJVTPpfy LmgGTg4noeIk9Ggh/lQOYrC1klD/mQy/yCzjWCfPCY3Wzcd2Kz0LTsrMIXjYlxcQdSrY tNMejIpr9ZtrgIwc7qPW8aejI0SYy9GygQU8RaxB5lJh5XFpJaNuDDE2XNL0FjdRo4Nr T+4w== 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 j30si2399911edd.363.2020.11.20.14.00.48; Fri, 20 Nov 2020 14:01:12 -0800 (PST) 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 S1728034AbgKTV6O (ORCPT + 99 others); Fri, 20 Nov 2020 16:58:14 -0500 Received: from ms.lwn.net ([45.79.88.28]:36810 "EHLO ms.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725805AbgKTV6O (ORCPT ); Fri, 20 Nov 2020 16:58:14 -0500 Received: from lwn.net (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ms.lwn.net (Postfix) with ESMTPSA id 16EB14FA; Fri, 20 Nov 2020 21:58:14 +0000 (UTC) Date: Fri, 20 Nov 2020 14:58:13 -0700 From: Jonathan Corbet To: Thorsten Leemhuis Cc: Randy Dunlap , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [RFC PATCH v2 00/26] Make reporting-bugs easier to grasp and yet more detailed & helpful Message-ID: <20201120145813.76b7b326@lwn.net> In-Reply-To: <2dcea97c-7b98-1ad2-d2ba-e7f7d77dc855@leemhuis.info> References: <20201113153313.68ff210c@lwn.net> <458eb542-ff4d-e734-67fd-01e8378d4864@leemhuis.info> <20201118172958.5b014a44@lwn.net> <2dcea97c-7b98-1ad2-d2ba-e7f7d77dc855@leemhuis.info> Organization: LWN.net MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 20 Nov 2020 11:46:07 +0100 Thorsten Leemhuis wrote: > Am 19.11.20 um 01:29 schrieb Jonathan Corbet: > > On Sun, 15 Nov 2020 11:13:52 +0100 > > Thorsten Leemhuis wrote: > > > - Collapse the whole thing down to a patch adding reporting-bugs-v2.rst > > (or some suitable name). I do wonder if it should also move to the > > process manual as part of this; not only admins will report bugs. > > After a night's sleep and Randy's comment I for now settled on > Documentation/admin-guide/reporting-issues.rst Keeping it in the admin guide is OK. Not sure about the name, though; if you're really dead set against bugs, maybe reporting-problems.rst? > > - Add a comment at the top saying it's a proposed replacement and > > soliciting comments. [...] > Struggled a bit to find the right words, but I think this should work: > > ``` > .. important:: > > This document is being prepared to replace > Documentation/admin-guide/reporting-bugs.rst. The main work is done and > you are already free to follow its instructions when reporting issues to > the Linux kernel developers. But keep in mind, below text still needs a > few finishing touches and review. It was merged to the Linux kernel > sources at this stage to make this process easier and increase the > text's visibility. > > Any improvements for the text or other feedback is thus very much > welcome. Please send it to 'Thorsten Leemhuis ' and > 'Jonathan Corbet ', ideally with 'Linux kernel mailing > list (LKML) ' and the 'Linux Kernel > Documentation List ' in CC. > > Areas in the text that still need work or discussion contain a hint > like this which point out the remaining issues; all of them start with > the word "FIXME" to make them easy to find. > ``` Seems OK. > > - In a separate patch you could add a comment to the existing document > > pointing to the new one as the true source of wisdom. > > This is what I plan to add: > > ``` > .. note:: > > Instead of reading below text consider reading this document > instead: Documentation/admin-guide/reporting-issues.rst. It's intended > to replace below text in the near future, as it's easier to grasp and > more straight forward; it also provides way more details and more > accurately describes the steps currently needed when reporting bugs to > the Linux developers. > ``` I'd be a bit more straightforward: This document is obsolete, and will be replaced by Documentation/admin-guide/$NAME in the near future. Not sure that more is really needed? jon