CVS update by vins xemacsweb/Develop ...

[email protected]
Newsgroups gmane.emacs.xemacs.cvs
Message-ID <[email protected]>
  User: vins    
  Date: 09/02/05 00:41:56

  Modified:    xemacsweb/Develop ChangeLog cvsaccess.content
Log:
Remove references to the 21.5 tree from CVS examples.

Revision  Changes    Path
1.110     +4 -0      XEmacs/xemacsweb/Develop/ChangeLog

Index: ChangeLog
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacsweb/Develop/ChangeLog,v
retrieving revision 1.109
retrieving revision 1.110
diff -u -p -r1.109 -r1.110
--- ChangeLog	2008/06/24 06:08:37	1.109
+++ ChangeLog	2009/02/04 23:41:55	1.110
@@ -1,3 +1,7 @@
+2009-01-31  Vin Shelton  <[email protected]>
+
+	* cvsaccess.content: Remove CVS directions for 21.5.
+
 2008-05-19  Stephen J. Turnbull  <[email protected]>
 
 	* hgaccess.content: Change incorrect reference to CVS to



1.32      +17 -24    XEmacs/xemacsweb/Develop/cvsaccess.content

Index: cvsaccess.content
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacsweb/Develop/cvsaccess.content,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -p -r1.31 -r1.32
--- cvsaccess.content	2008/02/02 07:27:20	1.31
+++ cvsaccess.content	2009/02/04 23:41:56	1.32
@@ -59,6 +59,12 @@ Stephen J. Turnbull &lt;[email protected]
     information, or for source/binary tarballs, check out the <a
       href="http://www.xemacs.org">XEmacs main WWW server</a>.</p>
 
+  <p>
+    The latest (21.5) development sources are no longer available
+    under CVS.  Please see the introduction to the <a
+      href="hgaccess.html">XEmacs Mercurial Repository</a> for
+    instructions on getting the 21.5 sources.
+
   <h3><a name="quickstart">Quick Start Guide</a></h3>
 
   <p>
@@ -69,11 +75,6 @@ $ <strong>cvs -d :pserver:[email protected]
 (Logging in to [email protected])
 CVS password: <strong>cvs</strong>
   </pre>
-  To get the latest (21.5) development sources, do:
-  <pre xml:space="preserve">
-    <strong>cvs -z3 -d :pserver:[email protected]:/pack/xemacscvs \
-      checkout -d xemacs-21.5 xemacs</strong>
-  </pre>
   To get the stable (21.4) development sources, do:
   <pre xml:space="preserve">
     <strong>cvs -z3 -d :pserver:[email protected]:/pack/xemacscvs \
@@ -93,7 +94,7 @@ CVS password: <strong>cvs</strong>
   </pre>
 
   <p>
-    Each of these components are available separately as non-CVS
+    Each of these components is available separately as non-CVS
     tarballs via ftp.  Here are the current URL's:</p>
   <ul>
     <li><a href="http://ftp.xemacs.org/pub/xemacs/xemacs-21.5"><strong>http://ftp.xemacs.org/pub/xemacs/xemacs-21.5</strong></a></li>
@@ -165,16 +166,16 @@ CVS password: <i>(not echoed)</i><strong
 
   <pre xml:space="preserve">
 pentagana [533]$ <strong>cvs -z3 -d :pserver:[email protected]:/pack/xemacscvs \
-      checkout -d xemacs-21.5 xemacs</strong>
+      checkout -d xemacs-21.4 -r release-21-4 xemacs</strong>
     <i>(churn, churn, churn)</i>
   </pre>
   <p>
-    And voila! One <strong>xemacs-21.5</strong> directory complete with the
+    And voila! One <strong>xemacs-21.4</strong> directory complete with the
     latest versions of the base code. Packages are separate, of
     course.</p>
 
   <p>
-    The <strong>-d</strong>option says what to name the new CVS directory
+    The <strong>-d</strong> option says what to name the new CVS directory
     tree.</p>
 
   <p>
@@ -186,12 +187,11 @@ pentagana [533]$ <strong>cvs -z3 -d :pse
       set this
       to <strong>-z9</strong>, but am now asking that you drop the compression
       rate. The gains in compression are not that great, and the
-      impact on my poor server can be tremendous...</font></p>
+      impact on the CVS server machine is significant.</font></p>
 
   <p>
-    The <strong>-r</strong> option specifies the CVS branch to use.  XEmacs 21.5
-    (the development version), is on the trunk ``branch'' (which has
-    no name), while XEmacs 21.1 uses the branch <strong>release-21-1</strong>,
+    The <strong>-r</strong> option specifies the CVS branch to use.
+    XEmacs 21.1 uses the branch <strong>release-21-1</strong>,
     which is in the same CVS module.  The branch is not named
     something like <strong>xemacs-21.1</strong>, because periods are not
     permitted in a valid CVS branch name.</p>
@@ -257,26 +257,19 @@ pentagana [533]$ <strong>cvs update</str
     commands, you can tell it which version to grab (however, they
     default to the most recent in the branch you're working on). All
     of the 21.x releases are tagged in the format rMAJOR-MINOR-RELEASE
-    (examples: XEmacs 21.5 beta 1 is tagged r21-5-1).  Yes, this
+    (examples: XEmacs 21.4.22 is tagged r21-4-22).  (Yes, this
     naming convention has changed from before.  Old tags had names
-    like r21-2b26.</p>
+    like r21-2b26.)</p>
 
   <p>
     The way you use this is by appending the <strong>-r &lt;TAG&gt;</strong>
     option to the CVS command you want to use. Therefore, to update to
-    21.5 beta 16 (but no further) from an earlier release, you'd
+    21.4.21 (but no further) from an earlier release, you'd
     type:</p>
 
   <pre xml:space="preserve">
-pentagana [533]$ <strong>cvs update -r r21-5-16</strong>
+pentagana [533]$ <strong>cvs update -r r21-4-21</strong>
   </pre>
-
-  <p>
-    For beta release on the trunk (XEmacs 21.5), there is a special
-    <strong>r21-5-latest-beta</strong> tag that you can use to always upgrade to
-    the latest released beta, but no further.  This way you can do
-    <strong>cvs update -r r21-5-latest-beta</strong> just once, and because the
-    tag is sticky, just do a simple <strong>cvs update</strong> thereafter.</p>
 
   <p>
     For more info, check your friendly CVS texinfo files.</p>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.