aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMaxim Konovalov <maxim@FreeBSD.org>2025-04-27 00:27:05 +0000
committerMaxim Konovalov <maxim@FreeBSD.org>2025-04-27 00:27:05 +0000
commite6a25a30be8f9d23cde6964c603db63cb3eefd60 (patch)
tree731574fdefab5f4acbca3c303d669c8da3a0965b
parent8f28a757b13aa8d1db6528453b4bd9df776271e9 (diff)
-rw-r--r--website/content/en/status/report-2025-01-2025-03/bugmeister.adoc2
1 files changed, 1 insertions, 1 deletions
diff --git a/website/content/en/status/report-2025-01-2025-03/bugmeister.adoc b/website/content/en/status/report-2025-01-2025-03/bugmeister.adoc
index d0591e9c01..75320b8a9d 100644
--- a/website/content/en/status/report-2025-01-2025-03/bugmeister.adoc
+++ b/website/content/en/status/report-2025-01-2025-03/bugmeister.adoc
@@ -29,7 +29,7 @@ Bugmeister folks also did some passes through the database to clean up metadata:
- obsoleted many stale patches where more than one patch was in the PR.
-The "automate harvesting PRs and evalauting whether they still apply" task has resulted in the release of link:https://github.com/linimon/patchQA[patchQA.py] as beta.
+The "automate harvesting PRs and evaluating whether they still apply" task has resulted in the release of link:https://github.com/linimon/patchQA[patchQA.py] as beta.
The program can take either a number (as a single PR number), or, with some work, a full REST query.
The main current problem is that the py-patch algorithm does not correctly handle fuzz.