From: Thorsten Leemhuis <email@example.com> To: Greg KH <firstname.lastname@example.org> Cc: Linus Torvalds <email@example.com>, Linux Kernel Mailing List <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org> Subject: Re: Thorsten is tracking regression again and could need a little help (was: Re: Linux 5.15) Date: Mon, 1 Nov 2021 14:34:21 +0100 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <YX/lnI5gX4TAF5Ea@kroah.com> On 01.11.21 14:03, Greg KH wrote: > On Mon, Nov 01, 2021 at 01:44:01PM +0100, Thorsten Leemhuis wrote: >> On 01.11.21 13:33, Greg KH wrote: >>> On Mon, Nov 01, 2021 at 05:49:40AM +0100, Thorsten Leemhuis wrote: >>>> example by simply forwarding the mail to firstname.lastname@example.org or >>>> CCing that address on a reply. I'll handle everything else then and tell >>>> regzbot about it. But if you feel adventurous, you can also skip me as >>>> the man-in-the-middle and tell the bot directly. To do that, just send a >>>> reply to the report to the regressions mailing list >>>> (email@example.com) either directly or by CCing it on a reply >>>> you would have written anyway; when doing so, place something like >>>> '#regzbot ^introduced v5.15..' (separated by blank lines) somewhere in >>>> the text, as outlined in regzbot's 'getting started guide' or its >>>> reference documentation: >>>> https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md >>>> https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md >>>> >>>> That's it, regzbot then on its next run will add the report to the list >>>> of tracked regression. I'll keep an eye on things and try to fix any >>>> problems I notice, as there likely will be a few. But then doesn't need >>>> to bother you. >>>> >>>> There is one thing that would really help: if one or two subsystem >>>> maintainers could give regzbot a shot for all the regression reports >>>> they get, even for easy fixes, as the bot really needs something to chew >>>> on. Any volunteers? >>> >>> I'll try it for the USB subsystem this merge cycle. >> >> That will be a great help, many thx. >> >>> Do you want a bug >>> report email redirected to that address or will a simple forward work >>> well enough? >> >> Redirecting will make it a little easier for me, but a simple forward is >> fine, too. > > Ok, I did that now for a USB bug report, hopefully that worked. If not, > I can forward it on. Got it, but I could need some advice on it if you have a minute. Does that report really look like a regression from your point of view? The part "The code has been this way in the kernel for a very long time, which suggests that it has been working, [...]" sounds like it is, but OTOH it's quite vague. I'm asking, because with my regression tracking work and regzbot I focus on regressions and ignore things that were always broken, as I (at least for now) don't want it to become yet another bug tracker (and I guess I would quickly drown in bugs as well). But if you think this case looks like a regression, I'll add it. Guess I just need to be creative then how to tell regzbot when it got introduced. Guess I'll settle on v2.6.13..v5.15", that should indicate there is something strange here. It's a use-case I hadn't expected. But well, that's why I wanted to something for testing. :-D Ciao, Thorsten
next prev parent reply other threads:[~2021-11-01 13:34 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <CAHk-=wjfbfQobW2jygMvgfJXKmzZNB=UTzBrFs2vTEzVpBXA4Q@mail.gmail.com> 2021-11-01 4:49 ` Thorsten Leemhuis 2021-11-01 11:46 ` Idzibear 2021-11-01 11:56 ` Greg KH 2021-11-01 12:54 ` Thorsten Leemhuis 2021-11-01 12:33 ` Greg KH 2021-11-01 12:44 ` Thorsten Leemhuis 2021-11-01 13:03 ` Greg KH 2021-11-01 13:34 ` Thorsten Leemhuis [this message] 2021-11-01 15:27 ` Greg KH 2021-11-01 16:19 ` 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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Thorsten is tracking regression again and could need a little help (was: Re: Linux 5.15)' \ /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).