[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-commits
Subject:    developer.kde.org/source
From:       Chris Howells <howells () kde ! org>
Date:       2004-01-20 20:02:54
Message-ID: 20040120200254.5FBDE1A27 () office ! kde ! org
[Download RAW message or body]

CVS commit by howells: 

add webcvs link


  M +1 -1      anoncvs.html   1.26


--- developer.kde.org/source/anoncvs.html  #1.25:1.26
@@ -56,5 +56,5 @@
     This, too, put unnecessary load on the server. Do one module at a time.
     </li>
-    <li>The various KDE modules have tags so it is possible to get a specifc release \
of KDE. Most KDE modules, apart from arts and kdeextragear-1 and kdeextragear-2, have \
a tag name in the format KDE_X_Y_Z_RELEASE (where X, Y and Z represent the exact \
version). The arts module has a different format of tag name, ARTS_X_Y_Z_RELEASE. The \
kdeextragear-1 and kdeextragear-2 modules do not have module-wide tags since each \
program is released individually; therefore you will need to check for the specific \
program what the correct tag is. For instance to get KDE 3.1, use +    <li>The \
various KDE modules have tags so it is possible to get a specifc release of KDE. Most \
KDE modules, apart from arts and kdeextragear-1 and kdeextragear-2, have a tag name \
in the format KDE_X_Y_Z_RELEASE (where X, Y and Z represent the exact version). The \
arts module has a different format of tag name, ARTS_X_Y_Z_RELEASE. The \
kdeextragear-1 and kdeextragear-2 modules do not have module-wide tags since each \
program is released individually; therefore you will need to check for the specific \
program what the correct tag is. <a href="http://webcvs.kde.org/">WebCVS</a> is a \
convenient way to check for a tag name. For instance to get KDE 3.1, use  <code>cvs \
co -r KDE_3_1_RELEASE</code>  </li>


[prev in list] [next in list] [prev in thread] [next in thread]