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

Updates for the Tracking a Development Branch section

Browse source 
Grammar tweaks for correctness and readability.

Add missing punctuation.

Prefer <application>svn</application> to <application>SVN</application>;
the latter occurred in only one place.

Remove a redundant list item about Subversion versus CTM.

Approved by:	hrs (mentor)
This commit is contained in:
Benjamin Kaduk 2013-07-02 12:48:18 +00:00
parent 75704c44f4
commit 1f12e4fe7a
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=42112
1 changed files with 8 additions and 15 deletions

23
en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml
View file

@ -1233,7 +1233,7 @@ Fetching 133 new ports or files... done.</screen>
<indexterm><primary>snapshot</primary></indexterm>
<para>&os.current; is the latest working sources for &os;.
<para>&os.current; is the very latest source code for &os;.
This includes work in progress, experimental changes, and
transitional mechanisms that might or might not be present
in the next official release of the software. While many
@ -1242,7 +1242,7 @@ Fetching 133 new ports or files... done.</screen>
buildable. These problems are resolved as quickly as
possible, but whether or not &os.current; brings disaster or
greatly desired functionality can be a matter of when the
source code was synced</para>
source code was synced.</para>
</sect3>
<sect3>
@ -1288,13 +1288,13 @@ Fetching 133 new ports or files... done.</screen>
</listitem>
<listitem>
<para>A quick way of getting bug fixes, though the fix is
<para>A quick way of getting bug fixes. Any given commit is
just as likely to introduce new bugs as to fix existing
ones.</para>
</listitem>
<listitem>
<para>In no way <quote>officially
<para>In any way <quote>officially
supported</quote>.</para>
</listitem>
</orderedlist>
@ -1467,7 +1467,7 @@ Fetching 133 new ports or files... done.</screen>
<para>For these reasons, one should <emphasis>not</emphasis>
blindly track &os.stable;. It is particularly important not
to update any production servers to &os.stable; without
first thoroughly testing the code in that development
first thoroughly testing the code in a development/testing
environment.</para>
<para>Except for those users who have the resources to perform
@ -1494,7 +1494,7 @@ Fetching 133 new ports or files... done.</screen>
to respond if they have any issues to raise concerning
the proposed change.</para>
<para>Join the relevant <application>SVN</application>
<para>Join the relevant <application>svn</application>
list for the branch being tracked. For example, users
tracking the 9-STABLE branch should join the
&a.svn-src-stable-9.name; list. This list records the
@ -1510,9 +1510,9 @@ Fetching 133 new ports or files... done.</screen>
</listitem>
<listitem>
<para>To install a new system in order to run monthly
<para>To install a new system running monthly
snapshots built from &os.stable;, refer to <ulink
url="&url.base;/snapshots/">Snapshots</ulink>for more
url="&url.base;/snapshots/">Snapshots</ulink> for more
information. Alternatively, it is possible to install
the most recent &os.stable; release from the <link
linkend="mirrors">mirror sites</link> and follow the
@ -1568,13 +1568,6 @@ Fetching 133 new ports or files... done.</screen>
</orderedlist>
</listitem>
<listitem>
<para>If you need rapid on-demand access to the source and
communications bandwidth is not a consideration, use
<application>Subversion</application>. Otherwise, use
<application>CTM</application>.</para>
</listitem>
<listitem>
<indexterm>
<primary>-STABLE</primary>