From: Jonathan Corbet <email@example.com> To: Thorsten Leemhuis <firstname.lastname@example.org>, Greg KH <email@example.com>, Linus Torvalds <firstname.lastname@example.org> Cc: 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: Thu, 08 Apr 2021 11:31:14 -0600 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> Thorsten Leemhuis <firstname.lastname@example.org> writes: > +In case you performed a successful bisection, use the title of the change that > +introduced the regression as the second part of your subject. Make the report > +also mention the commit id of the culprit. For tracking purposes, add a line > +like the following that contains both pieces of information, but with the > +commit id shortened to 12 characters:: > + > + #regzb introduced: 94a632d91ad1 ("usc: xhbi-foo: check bar_params earlier") > + > +In case of an unsuccessful bisection, make your report mention the latest tested > +version that's working fine (say 5.7) and the oldest where the issue occurs (say > +5.8-rc1). For tracking purposes add a line expressing it like this:: > + > + #regzb introduced: v5.7..v5.8-rc1 I kind of share Greg's concern that people aren't going to want to do this; it could even be seen as an impediment to reporting problems in general. If you *really* want random users to input this sort of information, you may well end up creating some sort of web page to step them through it. Also, though, as I understand it the system that will interpret these lines does not yet exist. Experience tells me that, as this system comes into existence, you will have a good chance of deciding that you want the syntax to look different anyway. So I would personally hold off on telling people to include directives like this until you have something that works with them. But that's just me... if this is the way it's going to work then the docs should of course reflect that. Thanks, jon
next prev parent reply other threads:[~2021-04-08 17:31 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 2021-04-07 11:21 ` Thorsten Leemhuis 2021-04-07 14:58 ` Greg KH 2021-04-08 17:31 ` Jonathan Corbet [this message] 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 \ --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 \ --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).