aboutsummaryrefslogtreecommitdiff
path: root/documentation/content/en/articles/committers-guide
diff options
context:
space:
mode:
authorEd Maste <emaste@FreeBSD.org>2025-05-23 19:40:50 +0000
committerEd Maste <emaste@FreeBSD.org>2025-05-23 19:46:12 +0000
commit554f43c0a7afc3e7e6d78611c8bb8fb41f7810e7 (patch)
treea27aaf67a5d0bfcd75f372ee80db22fbb8920864 /documentation/content/en/articles/committers-guide
parentfacf07474a1d39073b9d361154b8f7ca4ac276a1 (diff)
Diffstat (limited to 'documentation/content/en/articles/committers-guide')
-rw-r--r--documentation/content/en/articles/committers-guide/_index.adoc2
1 files changed, 1 insertions, 1 deletions
diff --git a/documentation/content/en/articles/committers-guide/_index.adoc b/documentation/content/en/articles/committers-guide/_index.adoc
index 91c14a89c1..f8a617ace1 100644
--- a/documentation/content/en/articles/committers-guide/_index.adoc
+++ b/documentation/content/en/articles/committers-guide/_index.adoc
@@ -3167,7 +3167,7 @@ There is no shame in asking "how in the heck do I do this?" We already know you
. Test your changes before committing them.
+
If your changes are to the kernel, make sure you can still compile both GENERIC and LINT.
-If your changes are anywhere else, make sure you can still make world.
+If your changes are anywhere else, make sure you can still compile userspace via `make buildworld`.
If your changes are to a branch, make sure your testing occurs with a machine which is running that code.
If you have a change which also may break another architecture, be sure and test on all supported architectures.
Please ensure your change works for