From: Greg KH <email@example.com> To: Thorsten Leemhuis <firstname.lastname@example.org> Cc: Jonathan Corbet <email@example.com>, Linus Torvalds <firstname.lastname@example.org>, Randy Dunlap <email@example.com>, firstname.lastname@example.org, email@example.com Subject: Re: [RFC PATCH v1 2/2] docs: reporting-issues: make everyone CC the regressions list Date: Wed, 7 Apr 2021 12:00:46 +0200 [thread overview] Message-ID: <YG2CztxS4jTia8wM@kroah.com> (raw) In-Reply-To: <firstname.lastname@example.org> On Wed, Apr 07, 2021 at 11:21:56AM +0200, Thorsten Leemhuis wrote: > Make people CC the recently created mailing list dedicated to Linux > kernel regressions when reporting one. Some paragraphs had to be > reshuffled and slightly rewritten during the process, as the text > otherwise would have gotten unnecessarily hard to follow. > > The new text also makes reporters include a line useful for automatic > regression tracking solution which does not exist yet, but is planned. > The term "#regzb" (short for regression bot) is inspired by the "#syz" > which can be used to communicate with syszbot (see > https://github.com/google/syzkaller/blob/master/docs/syzbot.md). While I understand the wish to automate things like this, the #syz marking will actually cause something to go off and do some work, and is only relevant for a very small number of developers, all of whom know to look up the instructions before doing so. But the #regzb marking will be requested to be added by random users who never have submitted a problem report before, OR from long-time kernel developers who are lucky to ever remember to read the documentation as they "know" how to do this. So this increased workload by people on the two ends of experience is going to be rough, I predict a very low rate of adoption :( What is the tag going to be good for? The reports will need to be handled by a person anyway and classified and tracked out-of-band from the list somehow. Will a tag do all that much here? thanks, greg k-h
next prev parent reply other threads:[~2021-04-07 10:02 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-07 9:21 [RFC PATCH v1 0/2] Add regression mailing list with basics for tracking Thorsten Leemhuis 2021-04-07 9:21 ` [RFC PATCH v1 1/2] MAINTAINERS: add regressions mailing list Thorsten Leemhuis 2021-04-07 9:56 ` Greg KH 2021-04-07 10:51 ` Thorsten Leemhuis 2021-04-07 14:56 ` Greg KH 2021-04-07 17:53 ` Thorsten Leemhuis 2021-04-07 9:21 ` [RFC PATCH v1 2/2] docs: reporting-issues: make everyone CC the regressions list Thorsten Leemhuis 2021-04-07 10:00 ` Greg KH [this message] 2021-04-07 11:21 ` Thorsten Leemhuis 2021-04-07 14:58 ` Greg KH 2021-04-08 17:31 ` Jonathan Corbet 2021-04-09 11:54 ` 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 \ --in-reply-to=YG2CztxS4jTia8wM@kroah.com \ --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: [RFC PATCH v1 2/2] docs: reporting-issues: make everyone CC the regressions list' \ /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).