CVS update [cvs1-11-x-branch]: /ccvs/

Tag: cvs1-11-x-branch
User: dprice  
Date: 05/05/02 10:07:22

Modified:
 /ccvs/
  ChangeLog, NEWS

Log:
 * NEWS: Note new val-tags locks.

File Changes:

Directory: /ccvs/
=================

File [changed]: ChangeLog
Url: https://ccvs.cvshome.org/source/browse/ccvs/ChangeLog?r1=1.692.2.205&r2=1.692.2.206
Delta lines:  +4 -0
-------------------
--- ChangeLog	30 Apr 2005 12:07:31 -0000	1.692.2.205
+++ ChangeLog	2 May 2005 17:07:19 -0000	1.692.2.206
@@ -1,3 +1,7 @@
+2005-05-02  Derek Price  <[email protected]>
+
+	* NEWS: Note new val-tags locks.
+
 2005-04-30  Derek Price  <[email protected]>
 
 	* NEWS: Note new history locks.

File [changed]: NEWS
Url: https://ccvs.cvshome.org/source/browse/ccvs/NEWS?r1=1.116.2.130&r2=1.116.2.131
Delta lines:  +8 -4
-------------------
--- NEWS	30 Apr 2005 12:07:31 -0000	1.116.2.130
+++ NEWS	2 May 2005 17:07:20 -0000	1.116.2.131
@@ -6,10 +6,14 @@
 * Thanks to an old report and patch from Stewart Brodie <[email protected]>, a
   potential crash in response to a corrupt RCS file has been fixed.
 
-* CVS now locks the history file before writing to it.  Especially with large
-  repositories, users should no longer see new warnings about corrupt history
-  records when using the `cvs history' command.  Existing corrupt history
-  records will still need to be removed.
+* CVS now locks the history and val-tags files before writing to them.
+  Especially with large repositories, users should no longer see new warnings
+  about corrupt history records when using the `cvs history' command.  Existing
+  corrupt history records will still need to be removed manually.  val-tags
+  corruption should have had less obvious effects, but removing the
+  CVSROOT/val-tags file and allowing a 1.11.21 or later version of CVS to
+  regenerate it may eliminate a few odd behaviors and possibly cause a slight
+  speed up of read transactions in large repositories over time.
 
 Changes from 1.11.19 to 1.11.20:
 ********************************