aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGraham Perrin <grahamperrin@gmail.com>2021-12-31 17:08:44 +0000
committerDanilo G. Baio <dbaio@FreeBSD.org>2021-12-31 17:09:50 +0000
commitde40a0d46fa6b0711f87ebe2b0d822682566f637 (patch)
treec357377cf7c695a2f620f1eb985910bedea980e5
parente8a6a98110ea377c2717da8d185f44bc30085a7d (diff)
downloaddoc-de40a0d46fa6b0711f87ebe2b0d822682566f637.tar.gz
doc-de40a0d46fa6b0711f87ebe2b0d822682566f637.zip
articles/problem-reports: Improve Mailing Lists phrase and fix its link
-rw-r--r--documentation/content/en/articles/problem-reports/_index.adoc2
1 files changed, 1 insertions, 1 deletions
diff --git a/documentation/content/en/articles/problem-reports/_index.adoc b/documentation/content/en/articles/problem-reports/_index.adoc
index 29bff9e428..24b63bb08a 100644
--- a/documentation/content/en/articles/problem-reports/_index.adoc
+++ b/documentation/content/en/articles/problem-reports/_index.adoc
@@ -272,7 +272,7 @@ When a problem report has not received attention after several weeks, it is wort
There are a few ways to do so, ideally in the following order, with a few days between attempting each communication channel:
-* Find the relevant FreeBSD mailing list for the problem report from the extref:{handbook}[list in the Handbook, eresources-mail] and send a message to that list asking about assistance or comments on the problem report.
+* Send an e-mail to extref:{handbook}eresources/[the relevant list, eresources-summary] seeking comments on the report.
* Join the relevant IRC channels. A partial listing is here: https://wiki.freebsd.org/IrcChannels[]. Inform the people in that channel about the problem report and ask for assistance. Be patient and stay in the channel after posting, so that the people from different time zones around the world have a chance to catch up.
* Find committers interested in the problem that was reported. If the problem was in a particular tool, binary, port, document, or source file, check the https://cgit.FreeBSD.org[Git Repository]. Locate the last few committers who made substantive changes to the file, and try to reach them via IRC or email. A list of committers and their emails can be found in the extref:{contributors}[Contributors to FreeBSD] article.