COMMIT
Is so happened due to a CVS conflict in Documentation/ChangeLog on
www.xemacs.org caused by me.
So I better document it.
Adrian
xemacsweb ChangeLog patch:
Diff command: cvs -q diff -U 0
Files affected: About/ChangeLog
Index: About/ChangeLog
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacsweb/About/ChangeLog,v
retrieving revision 1.189
diff -u -U0 -r1.189 ChangeLog
--- About/ChangeLog 17 Oct 2005 18:25:17 -0000 1.189
+++ About/ChangeLog 17 Oct 2005 19:21:14 -0000
@@ -2,0 +3,5 @@
+ * Website.content: Add note about failing "cvs update" causing
+ "make all" not to be run on master websites.
+
+2005-10-17 Adrian Aichner <adrian(a)xemacs.org>
+
xemacsweb source patch:
Diff command: cvs -f -z3 -q diff -u -w -N
Files affected: About/Website.content
Index: About/Website.content
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacsweb/About/Website.content,v
retrieving revision 1.68
diff -u -w -r1.68 Website.content
--- About/Website.content 20 Nov 2004 22:24:05 -0000 1.68
+++ About/Website.content 17 Oct 2005 19:20:36 -0000
@@ -298,6 +298,12 @@
all</cite> run.</p>
<p>
+ Please note that a failing <cite>cvs update</cite> (e.g. due to a
+ CVS conflict) will cause <cite>make all</cite> not to be run! CVS
+ conflicts on our master websites really need to be fixed
+ anyway.</p>
+
+ <p>
Commits also cause a mail message to be sent to the list
<a
href="http://list-archive.xemacs.org/xemacs-cvs/">xemacs-cvs...,
which is one of the XEmacs
--
Adrian Aichner
mailto:adrian@xemacs.org
http://www.xemacs.org/