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

Remove leftover references to svk.

Browse source
This commit is contained in:
Eitan Adler 2013-06-12 21:01:43 +00:00
parent 82e6e39154
commit 31349ce7ce
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=41915
1 changed files with 4 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -604,16 +604,13 @@
<title>Daily Use</title> <title>Daily Use</title>
<para>This section will explain how to perform common day-to-day <para>This section will explain how to perform common day-to-day
operations with Subversion. There should be no difference operations with Subversion.</para>
between <acronym>SVN</acronym> and <acronym>SVK</acronym> in
daily use, except for the revision renumbering mentioned
earlier.</para>
<sect3> <sect3>
<title>Help</title> <title>Help</title>
<para>Both <acronym>SVN</acronym> and <acronym>SVK</acronym> <para><acronym>SVN</acronym>
have built in help documentation. It can be accessed by has built in help documentation. It can be accessed by
typing the following command:</para> typing the following command:</para>
<screen>&prompt.user; <userinput>svn help</userinput></screen> <screen>&prompt.user; <userinput>svn help</userinput></screen>
@ -725,7 +722,7 @@
<title>Editing and Committing</title> <title>Editing and Committing</title>
<para>Unlike Perforce, <para>Unlike Perforce,
<acronym>SVN</acronym> and <acronym>SVK</acronym> do not <acronym>SVN</acronym> does not
need to be told in advance about file editing.</para> need to be told in advance about file editing.</para>
<para><command>svn commit</command> works like the equivalent <para><command>svn commit</command> works like the equivalent