From: Jonathan Corbet <email@example.com> To: Thorsten Leemhuis <firstname.lastname@example.org>, ksummit <email@example.com>, Greg KH <firstname.lastname@example.org>, Sasha Levin <email@example.com>, Randy Dunlap <firstname.lastname@example.org> Cc: Linux Kernel Mailing List <email@example.com>, firstname.lastname@example.org Subject: Re: [Ksummit-discuss] [1/5] reporting-issues: header and TLDR Date: Mon, 29 Mar 2021 16:44:21 -0600 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> Thorsten Leemhuis <email@example.com> writes: > FWIW, on another channel someone mentioned the process in the TLDR is > quite complicated when it comes to regressions in stable and longterm > kernels. I looked at the text and it seemed like a valid complaint, esp. > as those regressions are something we really care about. > > To solve this properly I sadly had to shake up the text in this section > completely and rewrite parts of it. Find the result below. I'm quite > happy with it, as it afaics is more straight forward and easier to > understand. And it matches the step-by-step guide better. And the best > thing: it's a bit shorter than the old TLDR. I think this is much improved - concise is good! :) I really just have one little comment... > I'll wait a day or two and then will send it through the regular review > together with a few small other fixes that piled up for the text, just > wanted to add it here for completeness. > > --- > The short guide (aka TL;DR) > =========================== > > Are you facing a regression with vanilla kernels from the same stable or > longterm series? One still supported? Then search the `LKML > <https://lore.kernel.org/lkml/>`_ and the `Linux stable mailing list > <https://lore.kernel.org/stable/>_` archives for matching reports to > join. If you don't find any, install `the latest release from that > series <https://kernel.org/>`_. If it still shows the issue, report it > to the stable mailing list and the stable maintainers. If we really want this to be a short guide that gets people to the answer quickly, we might as well put the addresses to report to right here rather than making people search for them. Thanks, jon _______________________________________________ Ksummit-discuss mailing list Ksummitfirstname.lastname@example.org https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
next prev parent reply other threads:[~2021-03-29 22:44 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-26 6:13 [Ksummit-discuss] FYI & RFC: obsoleting reporting-bugs and making reporting-issues official 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 [this message] 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
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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --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] [1/5] reporting-issues: header and TLDR' \ /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).