From: Mark Brown <email@example.com>
Subject: [Ksummit-discuss] [TECH TOPIC] Regression tracking & fixing: current state, problems, and next steps
Date: Thu, 16 Jun 2022 14:11:17 +0100 [thread overview]
Message-ID: <Yqsr9YBKLb8PNeVf@sirena.org.uk> (raw)
On Thu, Jun 16, 2022 at 02:49:40PM +0200, Thorsten Leemhuis wrote:
> - I see many mainline commits fixing regressions I never noticed, which
> made me wonder: is it a problem that I apparently seem to not become
> aware of many regressions reports? If the regression was fixed that
> obviously is not a problem. But it always makes me wonder how many
> regression reports are out there that were not addressed?
Especially in the embedded world an awful lot of reports come in the
form of fixes so there's no separate report.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 488 bytes
Desc: not available
prev parent reply other threads:[~2022-06-16 13:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 12:49 [Ksummit-discuss] [TECH TOPIC] Regression tracking & fixing: current state, problems, and next steps Thorsten Leemhuis
2022-06-16 13:11 ` Mark Brown [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).