COMMIT
SUPERSEDES <4q4bkt98.fsf(a)smtprelay.t-online.de>
Stephen I agree this smaller change makes more sense.
Could you please make any adjustments in the xemacs-builds module or
any personal scripts you may have, if necessary.
Best regards,
Adrian
xemacsweb ChangeLog patch:
Diff command: cvs -q diff -U 0
Files affected: Releases/ChangeLog Develop/ChangeLog
Index: Releases/ChangeLog
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacsweb/Releases/ChangeLog,v
retrieving revision 1.129
diff -u -U0 -r1.129 ChangeLog
--- Releases/ChangeLog 6 Jan 2006 11:55:58 -0000 1.129
+++ Releases/ChangeLog 12 Jan 2006 09:35:32 -0000
@@ -0,0 +1,11 @@
+2006-01-12 Adrian Aichner <adrian(a)xemacs.org>
+
+ * 21.5.19.content: Global replace of cvs tag r21-5-current-beta
+ with r21-5-latest-beta (reported by Simon Blanchard).
+ * 21.5.2.content: Ditto.
+ * 21.5.20.content: Ditto.
+ * 21.5.21.content: Ditto.
+ * 21.5.22.content: Ditto.
+ * 21.5.23.content: Ditto.
+ * 21.5.24.content: Ditto.
+
Index: Develop/ChangeLog
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacsweb/Develop/ChangeLog,v
retrieving revision 1.102
diff -u -U0 -r1.102 ChangeLog
--- Develop/ChangeLog 9 Jan 2006 20:45:18 -0000 1.102
+++ Develop/ChangeLog 12 Jan 2006 09:35:33 -0000
@@ -0,0 +1,6 @@
+2006-01-12 Adrian Aichner <adrian(a)xemacs.org>
+
+ * cvsaccess.content: Remove no longer needed <hr /> tag.
+ * packages.content: Remove misleading authorship and feedback
+ information (reported by Simon Blanchard).
+
xemacsweb source patch:
Diff command: cvs -f -z3 -q diff -u -w -N
Files affected: Releases/21.5.24.content Releases/21.5.23.content Releases/21.5.22.content
Releases/21.5.21.content Releases/21.5.20.content Releases/21.5.2.content
Releases/21.5.19.content Develop/packages.content Develop/cvsaccess.content
Index: Develop/cvsaccess.content
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacsweb/Develop/cvsaccess.content,v
retrieving revision 1.29
diff -u -w -r1.29 cvsaccess.content
--- Develop/cvsaccess.content 9 Jan 2006 20:45:19 -0000 1.29
+++ Develop/cvsaccess.content 12 Jan 2006 09:24:24 -0000
@@ -658,8 +658,6 @@
this may change to where the head is our development area, and you
will have to use tags to grab a particular version.</p>
- <hr />
-
<!-- Keep this comment at the end of the file
Local variables:
mode: xml
Index: Develop/packages.content
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacsweb/Develop/packages.content,v
retrieving revision 1.35
diff -u -w -r1.35 packages.content
--- Develop/packages.content 4 Apr 2005 19:29:38 -0000 1.35
+++ Develop/packages.content 12 Jan 2006 09:24:24 -0000
@@ -201,10 +201,6 @@
<a href="index.html">Back</a> to the How to Help page.
</p>
- <hr />
- This site used to be maintained by
- <address><a href="mailto:jareth@xemacs.org">Jareth
Hein</a></address>
-
<!-- Keep this comment at the end of the file
Local variables:
mode: xml
Index: Releases/21.5.19.content
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacsweb/Releases/21.5.19.content,v
retrieving revision 1.2
diff -u -w -r1.2 21.5.19.content
--- Releases/21.5.19.content 28 May 2005 08:48:18 -0000 1.2
+++ Releases/21.5.19.content 12 Jan 2006 09:24:26 -0000
@@ -116,7 +116,7 @@
will convert your entire tree.
Tags are also the same; to update to release 21.5.19, use the release
-tag "r21-5-19". The tag "r21-5-current-beta" will always be an
alias
+tag "r21-5-19". The tag "r21-5-latest-beta" will always be an alias
for the most recently released beta. Development occurs on the
unnamed CVS trunk; to revert your tree to the trunk, use "cvs update -A".
Index: Releases/21.5.2.content
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacsweb/Releases/21.5.2.content,v
retrieving revision 1.2
diff -u -w -r1.2 21.5.2.content
--- Releases/21.5.2.content 13 Jan 2003 21:37:14 -0000 1.2
+++ Releases/21.5.2.content 12 Jan 2006 09:24:28 -0000
@@ -33,7 +33,7 @@
permissions.
</p><p>
The CVS procedures are unchanged, and as far as I can tell the r21-5-2
-tag has been added and the r21-5-current-beta tag has been moved to
+tag has been added and the r21-5-latest-beta tag has been moved to
reflect the release. If there is a problem with CVS, any of the
reviewers with shell access at
ftp.xemacs.org should be able to fix.
Please do, I will be only intermittently able to access the 'net for
Index: Releases/21.5.20.content
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacsweb/Releases/21.5.20.content,v
retrieving revision 1.1
diff -u -w -r1.1 21.5.20.content
--- Releases/21.5.20.content 12 Mar 2005 07:12:48 -0000 1.1
+++ Releases/21.5.20.content 12 Jan 2006 09:24:28 -0000
@@ -297,7 +297,7 @@
will convert your entire tree.
Tags are also the same; to update to release 21.5.20, use the release
-tag "r21-5-20". The tag "r21-5-current-beta" will always be an
alias
+tag "r21-5-20". The tag "r21-5-latest-beta" will always be an alias
for the most recently released beta. Development occurs on the
unnamed CVS trunk; to revert your tree to the trunk, use "cvs update -A".
Index: Releases/21.5.21.content
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacsweb/Releases/21.5.21.content,v
retrieving revision 1.3
diff -u -w -r1.3 21.5.21.content
--- Releases/21.5.21.content 31 May 2005 22:36:47 -0000 1.3
+++ Releases/21.5.21.content 12 Jan 2006 09:24:29 -0000
@@ -103,7 +103,7 @@
To make it straightforward to access certain versions of the code, we have
a standard tagging policy. To update to release 21.5.21, use the update
flag "-r r21-5-21". To update to the current release without referring to
-it specifically, use the flag "-r r21-5-current-beta". To update to the
+it specifically, use the flag "-r r21-5-latest-beta". To update to the
latest commits in CVS, use the flag "-A". Then rebuild XEmacs.
Index: Releases/21.5.22.content
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacsweb/Releases/21.5.22.content,v
retrieving revision 1.1
diff -u -w -r1.1 21.5.22.content
--- Releases/21.5.22.content 19 Sep 2005 09:13:09 -0000 1.1
+++ Releases/21.5.22.content 12 Jan 2006 09:24:29 -0000
@@ -93,7 +93,7 @@
To make it straightforward to access certain versions of the code, we have
a standard tagging policy. To update to release 21.5.22, use the update
flag "-r r21-5-22". To update to the current release without referring to
-it specifically, use the flag "-r r21-5-current-beta". To update to the
+it specifically, use the flag "-r r21-5-latest-beta". To update to the
latest commits in CVS, use the flag "-A". Then rebuild XEmacs.
For more details, see
Index: Releases/21.5.23.content
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacsweb/Releases/21.5.23.content,v
retrieving revision 1.1
diff -u -w -r1.1 21.5.23.content
--- Releases/21.5.23.content 27 Oct 2005 18:29:34 -0000 1.1
+++ Releases/21.5.23.content 12 Jan 2006 09:24:29 -0000
@@ -104,7 +104,7 @@
To make it straightforward to access certain versions of the code, we have
a standard tagging policy. To update to release 21.5.23, use the update
flag "-r r21-5-23". To update to the current release without referring to
-it specifically, use the flag "-r r21-5-current-beta". To update to the
+it specifically, use the flag "-r r21-5-latest-beta". To update to the
latest commits in CVS, use the flag "-A". Then rebuild XEmacs.
For more details, see
Index: Releases/21.5.24.content
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacsweb/Releases/21.5.24.content,v
retrieving revision 1.1
diff -u -w -r1.1 21.5.24.content
--- Releases/21.5.24.content 19 Dec 2005 05:48:59 -0000 1.1
+++ Releases/21.5.24.content 12 Jan 2006 09:24:30 -0000
@@ -116,7 +116,7 @@
To make it straightforward to access certain versions of the code, we have
a standard tagging policy. To update to release 21.5.24, use the update
flag "-r r21-5-24". To update to the current release without referring to
-it specifically, use the flag "-r r21-5-current-beta". To update to the
+it specifically, use the flag "-r r21-5-latest-beta". To update to the
latest commits in CVS, use the flag "-A". Then rebuild XEmacs.
For more details, see
--
Adrian Aichner
mailto:adrian@xemacs.org
http://www.xemacs.org/