git: 9ab7d6510a - main - tiers: Remove obsolete language

From: Warner Losh <>
Date: Tue, 21 Feb 2023 16:40:00 UTC
The branch main has been updated by imp:


commit 9ab7d6510a448d4e061233ded450ddc9d19f44af
Author:     Warner Losh <>
AuthorDate: 2023-02-21 15:03:03 +0000
Commit:     Warner Losh <>
CommitDate: 2023-02-21 15:16:29 +0000

    tiers: Remove obsolete language
    amd64 is none of these things, so just remove the 'justifcation'
    sentence. It's wrong and fixing it wouldn't add any value.
    Sponsored by:           Netflix
    Differential Revision:
 documentation/content/en/articles/committers-guide/_index.adoc | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/documentation/content/en/articles/committers-guide/_index.adoc b/documentation/content/en/articles/committers-guide/_index.adoc
index 41ef2a507a..1082225e3a 100644
--- a/documentation/content/en/articles/committers-guide/_index.adoc
+++ b/documentation/content/en/articles/committers-guide/_index.adoc
@@ -3506,10 +3506,6 @@ In an effort to make it easier to keep FreeBSD portable across the platforms we
 Our 32-bit reference platform is i386, and our 64-bit reference platform is amd64.
 Major design work (including major API and ABI changes) must prove itself on at least one 32-bit and at least one 64-bit platform, preferably the primary reference platforms, before it may be committed to the source tree.
-The i386 and amd64 platforms were chosen due to being more readily available to developers and as representatives of more diverse processor and system designs - big versus little endian, register file versus register stack, different DMA and cache implementations, hardware page tables versus software TLB management etc.
-We will continue to re-evaluate this policy as cost and availability of the 64-bit platforms change.
 Developers should also be aware of our Tier Policy for the long term support of hardware architectures.
 The rules here are intended to provide guidance during the development process, and are distinct from the requirements for features and architectures listed in that section.
 The Tier rules for feature support on architectures at release-time are more strict than the rules for changes during the development process.