White space fix only. Translators can ignore.

Sponsored by:	iXsystems
This commit is contained in:
Dru Lavigne 2014-04-16 21:07:48 +00:00
parent 286b399080
commit e5c286ee17
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=44592

View file

@ -12,8 +12,7 @@
<acronym>DVD</acronym> Sets</title>
<para>&os; <acronym>CD</acronym> and <acronym>DVD</acronym> sets
are available from several online
retailers:</para>
are available from several online retailers:</para>
<itemizedlist>
<listitem>
@ -423,23 +422,23 @@ Comment out for now until these can be verified.
<title>Introduction</title>
<para>As of July 2012, &os; uses
<application>Subversion</application>
as the primary version control
system for storing all of &os;'s source code, documentation,
and the Ports Collection.</para>
<application>Subversion</application> as the primary version
control system for storing all of &os;'s source code,
documentation, and the Ports Collection.</para>
<note>
<para><application>Subversion</application> is generally a developer tool. Most users
should use <command>freebsd-update</command> (<xref
<para><application>Subversion</application> is generally a
developer tool. Most users should use
<command>freebsd-update</command> (<xref
linkend="updating-upgrading-freebsdupdate"/>) to update
the &os; base system, and <command>portsnap</command> (<xref
linkend="ports-using"/>) to
update the &os; Ports Collection.</para>
linkend="ports-using"/>) to update the &os; Ports
Collection.</para>
</note>
<para>This chapter demonstrates how to install
<application>Subversion</application> on a &os; system and then
use it to create a local copy of a &os; repository. It
<application>Subversion</application> on a &os; system and
then use it to create a local copy of a &os; repository. It
includes a list of the available &os;
<application>Subversion</application> mirrors and resources to
additional information on how to use
@ -489,14 +488,15 @@ Comment out for now until these can be verified.
</warning>
<para><application>Subversion</application> uses
<acronym>URL</acronym>s to designate a repository, taking the form of
<replaceable>protocol://hostname/path</replaceable>. Mirrors
may support different protocols as specified below. The first
component of the path is the &os; repository to access. There
are three different repositories, <literal>base</literal> for
the &os; base system source code, <literal>ports</literal> for
the Ports Collection, and <literal>doc</literal> for
documentation. For example, the URL
<acronym>URL</acronym>s to designate a repository, taking the
form of <replaceable>protocol://hostname/path</replaceable>.
Mirrors may support different protocols as specified below.
The first component of the path is the &os; repository to
access. There are three different repositories,
<literal>base</literal> for the &os; base system source code,
<literal>ports</literal> for the Ports Collection, and
<literal>doc</literal> for documentation. For example, the
URL
<literal>svn://svn0.us-east.FreeBSD.org/ports/head/</literal>
specifies the main branch of the ports repository on the
<systemitem
@ -595,7 +595,8 @@ Comment out for now until these can be verified.
</sect2>
<sect2 xml:id="svn-mirrors">
<title><application>Subversion</application> Mirror Sites</title>
<title><application>Subversion</application> Mirror
Sites</title>
<indexterm>
<primary>Subversion Repository</primary>
@ -607,16 +608,18 @@ Comment out for now until these can be verified.
<para>The master &os; <application>Subversion</application>
server, <systemitem
class="fqdomainname">svn.FreeBSD.org</systemitem>, is
publicly accessible, read-only. That may change in the future,
so users are encouraged to use one of the official mirrors. To
view the &os; <application>Subversion</application> repositories
through a browser, use <link
publicly accessible, read-only. That may change in the
future, so users are encouraged to use one of the official
mirrors. To view the &os;
<application>Subversion</application> repositories through a
browser, use <link
xlink:href="http://svnweb.FreeBSD.org/">http://svnweb.FreeBSD.org/</link>.</para>
<note>
<para>The &os; <application>Subversion</application> mirror network is still in its early days,
and will likely change. Do not count on this list of mirrors
being static. In particular, the <acronym>SSL</acronym> certificates of the
<para>The &os; <application>Subversion</application> mirror
network is still in its early days, and will likely change.
Do not count on this list of mirrors being static. In
particular, the <acronym>SSL</acronym> certificates of the
servers will likely change at some point.</para>
</note>
@ -692,8 +695,8 @@ Comment out for now until these can be verified.
<para><acronym>HTTPS</acronym> is the preferred protocol,
providing protection against another computer pretending to be
the &os; mirror (commonly known as a <quote>man in the
middle</quote> attack) or otherwise trying to send bad content
to the end user.</para>
middle</quote> attack) or otherwise trying to send bad
content to the end user.</para>
<para>On the first connection to an <acronym>HTTPS</acronym>
mirror, the user will be asked to verify the server
@ -717,9 +720,9 @@ Certificate information:
the server, and the verification step will be repeated on the
next connection. Accepting the certificate permanently will
store the authentication credentials in
<filename>~/.subversion/auth/</filename> and
the user will not be asked to verify the fingerprint again until
the certificate expires.</para>
<filename>~/.subversion/auth/</filename> and the user will not
be asked to verify the fingerprint again until the certificate
expires.</para>
<para>If <literal>https</literal> cannot be used due to firewall
or other problems, <literal>svn</literal> is the next choice,
@ -745,15 +748,14 @@ Certificate information:
<para>The following sites make &os; available through the rsync
protocol. The <application>rsync</application> utility works in
much the same way as the &man.rcp.1; command,
but has more options and uses the rsync remote-update protocol
which transfers only the differences between two sets of files,
thus greatly speeding up the synchronization over the network.
This is most useful if you are a mirror site for the
&os; <acronym>FTP</acronym> server, or the CVS repository. The
much the same way as the &man.rcp.1; command, but has more
options and uses the rsync remote-update protocol which
transfers only the differences between two sets of files, thus
greatly speeding up the synchronization over the network. This
is most useful if you are a mirror site for the &os;
<acronym>FTP</acronym> server, or the CVS repository. The
<application>rsync</application> suite is available for many
operating systems, on &os;, see the
<package>net/rsync</package>
operating systems, on &os;, see the <package>net/rsync</package>
port or use the package.</para>
<variablelist>
@ -881,7 +883,9 @@ Certificate information:
<para>This server may only be used by &os; primary mirror
sites.</para>
<para>Available collections:</para>
<itemizedlist>
<listitem>
<para>&os;: The master archive of the &os;