From: Thorsten Leemhuis <email@example.com> To: Greg KH <firstname.lastname@example.org> Cc: Linux Kernel Mailing List <email@example.com>, ksummit <firstname.lastname@example.org>, email@example.com Subject: Re: [Ksummit-discuss] FYI & RFC: obsoleting reporting-bugs and making reporting-issues official Date: Fri, 26 Mar 2021 10:48:56 +0100 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <YF2iYFEoc56sfeMx@kroah.com> 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 _______________________________________________ Ksummit-discuss mailing list Ksummitemail@example.com https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
prev parent reply other threads:[~2021-03-26 9:49 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-26 6:13 Thorsten Leemhuis 2021-03-26 6:15 ` [Ksummit-discuss] [1/5] reporting-issues: header and TLDR Thorsten Leemhuis 2021-03-26 6:23 ` Guenter Roeck 2021-03-26 9:41 ` Thorsten Leemhuis 2021-03-28 9:23 ` Thorsten Leemhuis 2021-03-28 10:03 ` Greg KH 2021-03-29 22:44 ` Jonathan Corbet 2021-03-30 5:59 ` Greg KH 2021-03-30 8:41 ` Thorsten Leemhuis 2021-03-26 6:16 ` [Ksummit-discuss] [2/5] reporting-issues: step-by-step-guide: main and two sub-processes for stable/longterm Thorsten Leemhuis 2021-03-26 8:57 ` Greg KH 2021-03-26 6:19 ` [Ksummit-discuss] [4/5] reporting-issues: reference section, stable and longterm sub-processes Thorsten Leemhuis 2021-03-26 6:19 ` [Ksummit-discuss] [5/5] reporting-issues: addendum Thorsten Leemhuis 2021-03-26 6:55 ` [Ksummit-discuss] FYI & RFC: obsoleting reporting-bugs and making reporting-issues official Thorsten Leemhuis 2021-03-26 6:57 ` [Ksummit-discuss] [3a/5] reporting-issues: reference section, main guide Thorsten Leemhuis 2021-03-26 6:59 ` [Ksummit-discuss] [3b/5] " Thorsten Leemhuis 2021-03-26 8:59 ` [Ksummit-discuss] FYI & RFC: obsoleting reporting-bugs and making reporting-issues official Greg KH 2021-03-26 9:48 ` Thorsten Leemhuis [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [Ksummit-discuss] FYI & RFC: obsoleting reporting-bugs and making reporting-issues official' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).