FreeBSD Bugzilla – Attachment 32695 Details for
Bug 53913
Various grammar fixes for committers article
Home
|
New
|
Browse
|
Search
|
[?]
|
Reports
|
Help
|
New Account
|
Log In
Remember
[x]
|
Forgot Password
Login:
[x]
[patch]
article.sgml.patch
article.sgml.patch (text/plain), 4.31 KB, created by
Chris Pepper
on 2003-06-30 03:20:19 UTC
(
hide
)
Description:
article.sgml.patch
Filename:
MIME Type:
Creator:
Chris Pepper
Created:
2003-06-30 03:20:19 UTC
Size:
4.31 KB
patch
obsolete
>Index: article.sgml >=================================================================== >RCS file: /home/ncvs/doc/en_US.ISO8859-1/articles/committers-guide/article.sgml,v >retrieving revision 1.166 >diff -u -r1.166 article.sgml >--- article.sgml 8 May 2003 10:21:18 -0000 1.166 >+++ article.sgml 30 Jun 2003 02:11:07 -0000 >@@ -1572,7 +1572,7 @@ > request a review of the decision after 30 days and every 30 days > thereafter (unless the total suspension period is less than 30 > days). A committer whose privileges have been revoked entirely >- may request a review after a period of 6 months have elapsed. >+ may request a review after a period of 6 months has elapsed. > This review policy is <emphasis>strictly informal</emphasis> > and, in all cases, core reserves the right to either act on or > disregard requests for review if they feel their original >@@ -1998,7 +1998,7 @@ > <para>FreeBSD is a highly portable operating system intended to > function on many different types of hardware architectures. > Maintaining clean separation of Machine Dependent (MD) and Machine >- Independent (MI) code, as well as minimizing MD code is an important >+ Independent (MI) code, as well as minimizing MD code, is an important > part of our strategy to remain agile with regards to current > hardware trends. Each new hardware architecture supported by > FreeBSD adds substantially to the cost of code maintenance, >@@ -2018,12 +2018,12 @@ > of interest in these environments, the FreeBSD Project is able > to maintain high levels of quality, stability, and performance, > as well as minimize the load on various support teams on the >- project, such as the ports team, documentation team, as well as >- security officer and release engineering teams. Diversity in >+ project, such as the ports team, documentation team, >+ security officer, and release engineering teams. Diversity in > hardware support broadens the options for FreeBSD consumers by > offering new features and usage opportunities (such as support >- for 64-bit CPUs, use in embedded environments), but these >- benefits always be carefully considered in terms of the real-world >+ for 64-bit CPUs, use in embedded environments, etc.), but these >+ benefits must always be carefully considered in terms of the real-world > maintenance cost associated with additional platform support. > </para> > >@@ -2032,7 +2032,7 @@ > requirements for an architecture to be in that tier, > as well as specifying the obligations of developers with > regards to the platform. In addition, a policy is defined >- regarding under the circumstances required to change the tier >+ regarding the circumstances required to change the tier > of an architecture.</para> > </sect2> > >@@ -2082,7 +2082,7 @@ > 2 status as the availability of resources to continue to maintain > the system in a Production Quality state diminishes.</para> > >- <para>Current Tier 2 platforms are PowerPC, and ia64.</para> >+ <para>Current Tier 2 platforms are PowerPC and ia64.</para> > </sect2> > > <sect2> >@@ -2094,7 +2094,7 @@ > platforms are architectures for which hardware is not or will not > be available to the project in the foreseeable future, for which > there are two or fewer active developers, that can not boot to at >- least single-user mode on real hardware (or simulator for new >+ least single-user mode on real hardware (or a simulator for new > hardware platforms), or which are considered legacy systems > unlikely to see broad future use. Tier 3 systems will not be > committed to the base source tree, although support for Tier 3 >@@ -2118,7 +2118,7 @@ > <sect2> > <title>Policy on Changing the Tier of an Architecture</title> > >- <para>Systems may only be moved from one tier to another tier by >+ <para>Systems may only be moved from one tier to another by > approval of the FreeBSD Core Team, which shall make that > decision in collaboration with the Security Officer, Release > Engineering, and toolchain maintenance teams.</para> >@@ -2668,7 +2668,7 @@ > well.</para> > > <para>This information consists of one or more lines containing the >- the key word or phrase, a colon, tabs for formatting, and then the >+ key word or phrase, a colon, tabs for formatting, and then the > additional information.</para> > > <para>The key words or phrases are:</para>
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Diff
View Attachment As Raw
Actions:
View
|
Diff
Attachments on
bug 53913
: 32695