os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

committer guide: igor and whitespace cleanup

Browse source 
- clean up whitespace in committer guide
This commit is contained in:
Eitan Adler 2015-04-26 16:31:29 +00:00
parent d3c4036af0
commit 5044b02740
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=46604
1 changed files with 33 additions and 29 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

58
en_US.ISO8859-1/articles/committers-guide/article.xml
View file

@ -323,17 +323,20 @@ You need a Passphrase to protect your secret key.</screen>
<sect1 xml:id="kerberos-ldap"> <sect1 xml:id="kerberos-ldap">
<title>Kerberos and LDAP web Password for &os; Cluster</title> <title>Kerberos and LDAP web Password for &os; Cluster</title>
<para>The &os; cluster requires a Kerberos password to access certain <para>The &os; cluster requires a Kerberos password to access
services. The Kerberos password also serves as the LDAP web password, certain services. The Kerberos password also serves as the
since LDAP is proxying to Kerberos in the cluster. Some of the services LDAP web password, since LDAP is proxying to Kerberos in the
cluster. Some of the services
which require this include:</para> which require this include:</para>
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para><link xlink:href="https://bugs.freebsd.org/bugzilla">Bugzilla</link></para> <para><link
xlink:href="https://bugs.freebsd.org/bugzilla">Bugzilla</link></para>
</listitem> </listitem>
<listitem> <listitem>
<para><link xlink:href="https://jenkins.freebsd.org">Jenkins</link></para> <para><link
xlink:href="https://jenkins.freebsd.org">Jenkins</link></para>
</listitem> </listitem>
</itemizedlist> </itemizedlist>
@ -416,15 +419,15 @@ You need a Passphrase to protect your secret key.</screen>
of the tree where the work is occurring.</para> of the tree where the work is occurring.</para>
<sect2> <sect2>
<title>Policy for Committer Activity In Other Trees</title> <title>Policy for Committer Activity in Other Trees</title>
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para>All committers may modify <para>All committers may modify
<filename>base/head/share/misc/committers-*.dot</filename>, <filename>base/head/share/misc/committers-*.dot</filename>,
<filename>base/head/usr.bin/calendar/calendars/calendar.freebsd</filename>, <filename>base/head/usr.bin/calendar/calendars/calendar.freebsd</filename>,
and and
<filename>ports/head/astro/xearth/files</filename>.</para> <filename>ports/head/astro/xearth/files</filename>.</para>
</listitem> </listitem>
<listitem> <listitem>
@ -2462,8 +2465,7 @@ ControlPersist yes</screen>
<para>Avoid obfuscating the email address of the <para>Avoid obfuscating the email address of the
submitter as this adds additional work when searching submitter as this adds additional work when searching
logs.</para> logs.</para></entry>
</entry>
</row> </row>
<row> <row>
@ -2928,7 +2930,8 @@ Relnotes: yes</programlisting>
build infrastructure, approving new documentation build infrastructure, approving new documentation
committers, and ensuring that the &os; website and committers, and ensuring that the &os; website and
documentation on the FTP site is up to date with respect documentation on the FTP site is up to date with respect
to the <application>subversion</application> tree. It is not a conflict resolution body. to the <application>subversion</application> tree. It is
not a conflict resolution body.
The vast majority of documentation related discussion The vast majority of documentation related discussion
takes place on the &a.doc;. More details regarding the takes place on the &a.doc;. More details regarding the
doceng team can be found in its <link doceng team can be found in its <link
@ -3801,16 +3804,16 @@ Relnotes: yes</programlisting>
Tier 3 platforms are architectures in the early stages of Tier 3 platforms are architectures in the early stages of
development, for non-mainstream hardware platforms, or which development, for non-mainstream hardware platforms, or which
are considered legacy systems unlikely to see broad future are considered legacy systems unlikely to see broad future
use. Initial support for Tier 3 platforms should be worked on in use. Initial support for Tier 3 platforms should be worked on
external SCM repositories. in external SCM repositories.
The transition to &os;'s subversion should take place after The transition to &os;'s subversion should take place after
the platform boots multi-user on hardware; sharing via the platform boots multi-user on hardware; sharing via
subversion is needed for wider exposure; and multiple subversion is needed for wider exposure; and multiple
developers are actively working on the platform. developers are actively working on the platform.
Platforms that transition to Tier 3 status may be Platforms that transition to Tier 3 status may be
removed from the tree if they are no longer actively supported by the removed from the tree if they are no longer actively supported
&os; developer community at the discretion of the release by the &os; developer community at the discretion of the
engineer.</para> release engineer.</para>
<para>Tier 3 platforms may have ports support, either integrated <para>Tier 3 platforms may have ports support, either integrated
or external, but do not require it.</para> or external, but do not require it.</para>
@ -3830,8 +3833,8 @@ Relnotes: yes</programlisting>
project.</para> project.</para>
<para>All systems not otherwise classified into a support tier <para>All systems not otherwise classified into a support tier
are Tier 4 systems. The &arch.ia64; platform is transitioning to are Tier 4 systems. The &arch.ia64; platform is transitioning
Tier 4 status in &os; 11.</para> to Tier 4 status in &os; 11.</para>
</sect2> </sect2>
<sect2> <sect2>
@ -4003,9 +4006,9 @@ Relnotes: yes</programlisting>
<important> <important>
<para>Do not use <command>svn add</command> to add the <para>Do not use <command>svn add</command> to add the
port. Follow these steps. If they are unclear, or are port. Follow these steps. If they are unclear, or
not working, ask for help, do not just <command>svn are not working, ask for help, do not just
add</command> the port.</para> <command>svn add</command> the port.</para>
</important> </important>
<procedure> <procedure>
@ -4755,8 +4758,7 @@ Property changes on: 2015Q1
___________________________________________________________________ ___________________________________________________________________
Modified: svn:mergeinfo Modified: svn:mergeinfo
Merged /head:r380362 Merged /head:r380362
Do you want to commit? (no = start a shell) [y/n] Do you want to commit? (no = start a shell) [y/n]</screen>
</screen>
<para>At that point, the script will either open a shell <para>At that point, the script will either open a shell
for you to fix things, or open your text editor with the for you to fix things, or open your text editor with the
@ -5002,9 +5004,11 @@ Do you want to commit? (no = start a shell) [y/n]
<para>In addition, developers may request a cloaked hostmask <para>In addition, developers may request a cloaked hostmask
for their account on the Freenode IRC network in the form for their account on the Freenode IRC network in the form
of of
<literal>freebsd/developer/</literal><replaceable>freefall name</replaceable> <literal>freebsd/developer/</literal><replaceable>freefall
name</replaceable>
or or
<literal>freebsd/developer/</literal><replaceable>NickServ name</replaceable>. <literal>freebsd/developer/</literal><replaceable>NickServ
name</replaceable>.
To request a cloak, send an email To request a cloak, send an email
to &a.irc.email; with your requested hostmask and to &a.irc.email; with your requested hostmask and
NickServ account name.</para> NickServ account name.</para>