Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp1181022pxf; Fri, 26 Mar 2021 02:50:44 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzUm2HZfkyu0+jQMfeWgIrWd+0J4kNDfowx49uqK8KhIXb1b6U18/rKamq+1UYJGoL4I7Kv X-Received: by 2002:aa7:d98b:: with SMTP id u11mr14335523eds.352.1616752244697; Fri, 26 Mar 2021 02:50:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1616752244; cv=none; d=google.com; s=arc-20160816; b=EhqF9pJiUmWvfR6veZ4prOhs6ujZDpHws4fw8UWjXxBuJEecxGmJUtOWKLEPhDrjam 4R3mK9i7BH3RspKQEWo2+ZqwPhnkftMKlITAnubcRTbocX1E7vYbcrPETmNhi3EyLeFG 481pcBkixSYaQYklUl+7c4zpUE0qNOs2h7EN1K8+BPWbVlNv/5IbkiRbTRwsUhqSoIqZ JOIJIEiCvBeh2VFfEITYYsrivwT77pHuJ/3rTmBHL5AWKfamDLfAsNW4hxHxKD5DUkTT RluYyIFZfoUCGiDTmUpbIT3Yv3kwxS46pfrm/GvfD5Uri3Dqc6ZXACvTbkogwkvfiDLN 4yew== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:subject:from :references:cc:to; bh=41pJy611t1Y0IeESTJK2ismTTVRrKMTpI4X2fjtzMbQ=; b=PYno3RiK97nmyKhuy8l4Wb5MwKhH65aAMEkFfzzsyffNCp/vzuEU1duBOjlJU/gU0i NmGS1Fkju35WYzUvZasknB7XNsYxPUPsN6Lg7Gxcx2iRbiQ9j9/+kSwC96zT3cCK+0Fy R3XEJLmXS0ZnYgYXjPPJ/UNG3VSdoc6oXQvKU6xZHUH3AcinoD5KoyoLJXrpHDyVo9Q0 g+jch0tYPXgre10vILAqlZsZAGTY+eTcgKuwHGso5Fod5XVIqLGwcfX7p4h138IE+7Ru V7RPIluPRztrxylmyiHfN/9ZYHZoXVj5Wsn7cc95ArUTSeTOvAknM0t72N33w0Xhcx5P LQkg== 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 q8si6495686ejr.208.2021.03.26.02.50.21; Fri, 26 Mar 2021 02:50:44 -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 S229589AbhCZJtI (ORCPT + 99 others); Fri, 26 Mar 2021 05:49:08 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47434 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229474AbhCZJtA (ORCPT ); Fri, 26 Mar 2021 05:49:00 -0400 Received: from wp530.webpack.hosteurope.de (wp530.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8234::]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BAE21C0613AA; Fri, 26 Mar 2021 02:48:59 -0700 (PDT) Received: from ip4d142c50.dynamic.kabel-deutschland.de ([77.20.44.80] helo=[192.168.66.200]); authenticated by wp530.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1lPj5M-0005ls-Of; Fri, 26 Mar 2021 10:48:56 +0100 To: Greg KH Cc: ksummit , Sasha Levin , Linux Kernel Mailing List , linux-doc@vger.kernel.org References: From: Thorsten Leemhuis Subject: Re: [Ksummit-discuss] FYI & RFC: obsoleting reporting-bugs and making reporting-issues official Message-ID: <10737257-cfb5-b24b-4f37-a53fd791fb73@leemhuis.info> Date: Fri, 26 Mar 2021 10:48:56 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-BS Content-Transfer-Encoding: 8bit X-bounce-key: webpack.hosteurope.de;linux@leemhuis.info;1616752139;d35e3131; X-HE-SMSGID: 1lPj5M-0005ls-Of Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 26.03.21 09:59, Greg KH wrote: > On Fri, Mar 26, 2021 at 07:13:09AM +0100, Thorsten Leemhuis wrote: >> >> Lo! Since a few months mainline in >> Documentation/admin-guide/reporting-issues.rst contains a text written >> to obsolete the good old reporting-bugs text. For now, the new document >> still contains a warning at the top that basically says "this is WIP". >> But I'd like to remove that warning and delete reporting-bugs.rst in the >> next merge window to make reporting-issues.rst fully official. With this >> mail I want to give everyone a chance to take a look at the text and >> speak up if you don't want me to move ahead for now. >> >> For easier review I'll post the text of reporting-issues.rst in reply to >> this mail. I'll do that in a few chunks, as if this was a cover letter >> for a patch-set. Note, the version I'll send in some areas looks a bit >> different from the one currently in mainline. That's because the text >> I'll send already incorporates a few patches from docs-next that are >> waiting for the next merge window; I also removed the "WIP" box as well >> as two remaining "FIXME" notes, as those point to aspects I mention >> below already. >> >> @Greg, @Sasha, I'd be especially glad if at least one of you two could >> take a look and yell if there is something you really dislike from the >> perspective of the stable maintainers. > > I responded to the specific email, but will again here. No objection > from me at all, Thx for taking a look! > this is a great resource, thanks for doing this. Very glad to hear, thx. > If, > over time, it needs any tweaks to explain things that people commonly > get wrong, that's easy to do, Which likely will be the case, but that's life. :-D > so don't worry about trying to capture > "everything" right away. Hah, I'm not worried about that (but yes, I have a tendency in that direction...). I just feared something along the lines of "ohh, this is all wrong, who sneaked this into the kernel behind our back". ;-) Ciao, Thorsten