svn commit: r49291 - head/en_US.ISO8859-1/articles/committers-guide

[John Baldwin]

On 8/16/16 6:18 AM, Brad Davis wrote:
> Author: brd
> Date: Tue Aug 16 13:18:00 2016
> New Revision: 49291
> URL: https://svnweb.freebsd.org/changeset/doc/49291
> 
> Log:
>   Update the reference 64-bit arch and remove a blurb about ia64 vs sparc64.
>   
>   Reported by:	mat
>   Reviewed by:	bcr

This needs a bit more work.  This change is ok (sparc64 simply isn't
prevelant), but it is not as simple a change as this commit implies.

> Modified:
>   head/en_US.ISO8859-1/articles/committers-guide/article.xml
> 
> Modified: head/en_US.ISO8859-1/articles/committers-guide/article.xml
> ==============================================================================
> --- head/en_US.ISO8859-1/articles/committers-guide/article.xml	Tue Aug 16 12:29:51 2016	(r49290)
> +++ head/en_US.ISO8859-1/articles/committers-guide/article.xml	Tue Aug 16 13:18:00 2016	(r49291)
> @@ -3614,24 +3614,20 @@ Relnotes:           yes</programlisting>
>  
>        <blockquote>
>  	<para>Our 32-bit reference platform is &arch.i386;, and our
> -	  64-bit reference platform is &arch.sparc64;.  Major design
> +	  64-bit reference platform is &arch.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.</para>
>        </blockquote>
>  
> -      <para>The &arch.i386; and &arch.sparc64; platforms were chosen
> +      <para>The &arch.i386; and &arch.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.</para>

None of these differences are now true.  Both are little endian,
both use a register file, both use the same DMA and cache implementation,
and both use hardware page tables.  I think you need to axe this entire
paragraph.

-- 
John Baldwin