Whitespace-only fixes, translators please ignore.

This commit is contained in:
Warren Block 2014-11-06 03:33:44 +00:00
parent 3c5e1f1f1c
commit 1e07a71a55
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=45942

View file

@ -304,7 +304,8 @@ You need a Passphrase to protect your secret key.</screen>
<link
xlink:href="http://www.iusmentis.com/security/passphrasefaq/"></link>,
<link xlink:href="http://xkcd.com/936/"></link>,
<link xlink:href="http://en.wikipedia.org/wiki/Passphrase"></link>.</para>
<link
xlink:href="http://en.wikipedia.org/wiki/Passphrase"></link>.</para>
</step>
</procedure>
@ -2864,23 +2865,23 @@ Relnotes: yes</programlisting>
<sect1 xml:id="gnats">
<title>Bugzilla</title>
<para>The &os; Project utilizes <application>Bugzilla</application>
for tracking bugs and change requests. Be sure that if you
commit a fix or suggestion found in the PR database to close it.
It is also
considered nice if you take time to close any PRs associated
with your commits, if appropriate.</para>
<para>The &os; Project utilizes
<application>Bugzilla</application> for tracking bugs and change
requests. Be sure that if you commit a fix or suggestion found
in the PR database to close it. It is also considered nice if
you take time to close any PRs associated with your commits, if
appropriate.</para>
<para>Committers with
non-<systemitem class="domainname">&os;.org</systemitem>
Bugzilla accounts can have the old account merged with the
<systemitem class="domainname">&os;.org</systemitem> account by
entering a new bug. Choose <literal>Supporting Services</literal>
as the Product, and <literal>Bug Tracker</literal> as the
Component.</para>
entering a new bug. Choose
<literal>Supporting Services</literal> as the Product, and
<literal>Bug Tracker</literal> as the Component.</para>
<para>You can find out more about <application>Bugzilla</application>
at:</para>
<para>You can find out more about
<application>Bugzilla</application> at:</para>
<itemizedlist>
<listitem>
@ -3842,17 +3843,16 @@ Relnotes: yes</programlisting>
copies.</para>
<para>The easiest way to add a new port is the
<command>addport</command> script
located in the <filename>ports/Tools/scripts</filename>
directory. It adds a port from the directory
specified, determining the category automatically from the
port <filename>Makefile</filename>. It also adds an
entry to the port's category
<filename>Makefile</filename>. It was written by
&a.mharo.email;, &a.will.email;, and &a.garga.email;.
When sending
questions about this script to the &a.ports;, please
also CC &a.crees.email;, the current maintainer.</para>
<command>addport</command> script located in the
<filename>ports/Tools/scripts</filename> directory. It
adds a port from the directory specified, determining
the category automatically from the port
<filename>Makefile</filename>. It also adds an entry to
the port's category <filename>Makefile</filename>. It
was written by &a.mharo.email;, &a.will.email;, and
&a.garga.email;. When sending questions about this
script to the &a.ports;, please also CC &a.crees.email;,
the current maintainer.</para>
</answer>
</qandaentry>
@ -4031,10 +4031,11 @@ Relnotes: yes</programlisting>
</procedure>
<tip>
<para>The <command>addport</command> script mentioned in <xref linkend="ports-qa-adding"/> now detects when the
port to add has previously existed, and attempts to handle
all except the <filename>ports/LEGAL</filename> step
automatically.</para>
<para>The <command>addport</command> script mentioned in
<xref linkend="ports-qa-adding"/> now detects when the
port to add has previously existed, and attempts to
handle all except the <filename>ports/LEGAL</filename>
step automatically.</para>
</tip>
</answer>
</qandaentry>
@ -4637,11 +4638,10 @@ bak/packages packages from last complete &lt;major_version&gt; run on &lt;arch&
Committers</title>
<para>A few people who have access to the &os; machines do not
have commit bits. Almost all of this document will apply to
these developers
as well (except things specific to commits and the mailing list
memberships that go with them). In particular, we recommend
that you read:</para>
have commit bits. Almost all of this document will apply to
these developers as well (except things specific to commits and
the mailing list memberships that go with them). In particular,
we recommend that you read:</para>
<itemizedlist>
<listitem>