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

[email protected] 2 May 2005 20:03:19 -0000
Newsgroups gmane.comp.version-control.cvs.cvs
Message-ID <[email protected]>
Tag: cvs1-11-x-branch
User: dprice  
Date: 05/05/02 13:03:19

Modified:
 /ccvs/
  ChangeLog, TODO

Log:
 * TODO (231): New item.
 (22, 30, 31): Remove completed items.

File Changes:

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

File [changed]: ChangeLog
Url: https://ccvs.cvshome.org/source/browse/ccvs/ChangeLog?r1=1.692.2.206&r2=1.692.2.207
Delta lines:  +5 -0
-------------------
--- ChangeLog	2 May 2005 17:07:19 -0000	1.692.2.206
+++ ChangeLog	2 May 2005 20:03:17 -0000	1.692.2.207
@@ -1,5 +1,10 @@
 2005-05-02  Derek Price  <[email protected]>
 
+	* TODO (231): New item.
+	(22, 30, 31): Remove completed items.
+
+2005-05-02  Derek Price  <[email protected]>
+
 	* NEWS: Note new val-tags locks.
 
 2005-04-30  Derek Price  <[email protected]>

File [changed]: TODO
Url: https://ccvs.cvshome.org/source/browse/ccvs/TODO?r1=1.72.4.6&r2=1.72.4.7
Delta lines:  +5 -11
--------------------
--- TODO	25 Aug 2004 03:31:57 -0000	1.72.4.6
+++ TODO	2 May 2005 20:03:17 -0000	1.72.4.7
@@ -1,16 +1,5 @@
 The "TODO" file!                              -*-Indented-Text-*-
 
-22. Catch signals for cleanup when "add"ing files.
-
-30. Add "rdiff" & "rtag" program options to the modules database.  These
-    commands seem hard to use since these commands deal directly with the
-    RCS ,v files.  (perhaps should think a little harder about what this is
-    trying to accomplish and what the best way is -kingdon, Jul 1997).
-
-31. Think hard about ^C recovery.
-    One particular issue: RCS removes the ,foo.c, file on ^C and CVS
-    doesn't.
-
 38. Think hard about using RCS state information to allow one to checkin
     a new vendor release without having it be accessed until it has been
     integrated into the local changes.
@@ -869,3 +858,8 @@
 
 230.  Support for options like compression as part of the CVSROOT might be
 nice.  This should be fairly easy to implement now using the method options.
+
+231.  Noop commands should be logged in the history file.  Information can
+still be obtained with noop commands, for instance via `cvs -n up -p', and
+paranoid admins might appreciate this.  Similarly, perhaps diff operations
+should be logged.