It is no longer possible to export parts of the Perforce tree to the

CVSup mirror network.
This commit is contained in:
Gavin Atkinson 2014-05-17 17:12:57 +00:00
parent 78b3bb7a8c
commit 9fbe7de7b8
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=44858

View file

@ -15,7 +15,6 @@
<legalnotice xml:id="trademarks" role="trademarks">
&tm-attrib.freebsd;
&tm-attrib.cvsup;
&tm-attrib.general;
</legalnotice>
@ -58,9 +57,7 @@
<para>The &os; <application>Perforce</application> server is
hosted on <systemitem class="fqdomainname">perforce.freebsd.org</systemitem>,
port <literal>1666</literal>. The repository is browsable
online at <uri xlink:href="http://p4web.freebsd.org">http://p4web.freebsd.org</uri>.
Some portions of the repository are also automatically exported
to a number of legacy <application>CVSup</application> servers.</para>
online at <uri xlink:href="http://p4web.freebsd.org">http://p4web.freebsd.org</uri>.</para>
</sect2>
</sect1>
@ -808,12 +805,7 @@
<para>The bridge between Subversion and <application>Perforce</application>
is one-way; changes to Subversion will be reflected in
<application>Perforce</application>, but changes in Perforce will
not be reflected in Subversion. On request, some parts of the
<application>Perforce</application> repo can be exported to
<application>CVSup</application> and made available for
distribution that way. Contact the &os;
<application>Perforce</application> administrators if this is
something that you are interested in.</para>
not be reflected in Subversion.</para>
</sect1>
<sect1 xml:id="offline-ops">
@ -823,7 +815,7 @@
assumes that network access to the server is always available.
Most state, history, and metadata is saved on the server, and
there is no provision for replicating the server like there is
with CVS/<application>CVSup</application>. It is possible to run
with SVN. It is possible to run
a proxy server, but it only provides very limited utility for
offline operation.</para>