cvs-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Cvs-cvs] Changes to ccvs/src/entries.c


From: Derek Robert Price
Subject: [Cvs-cvs] Changes to ccvs/src/entries.c
Date: Wed, 21 Sep 2005 22:22:43 -0400

Index: ccvs/src/entries.c
diff -u ccvs/src/entries.c:1.65 ccvs/src/entries.c:1.66
--- ccvs/src/entries.c:1.65     Tue May 24 20:59:01 2005
+++ ccvs/src/entries.c  Thu Sep 22 02:22:41 2005
@@ -942,23 +942,7 @@
    base_deregister and base_register is the kind of thing we used to
    do for Entries and which turned out to be slow, which is why there
    is now the Entries.Log machinery.  So maybe from that point of
-   view it is a mistake to do this separately from Entries, I dunno.
-
-   We also need something analogous for:
-
-   1. CVS/Template (so we can update the Template file automagically
-   without the user needing to check out a new working directory).
-   Updating would probably print a message (that part might be
-   optional, although probably it should be visible because not all
-   cvs commands would make the update happen and so it is a
-   user-visible behavior).  Constructing version number for template
-   is a bit hairy (base it on the timestamp on the server?  Or see if
-   the template is in checkoutlist and if yes use its versioning and
-   if no don't version it?)....
-
-   2.  cvsignore (need to keep a copy in the working directory to do
-   "cvs release" on the client side; see comment at src/release.c
-   (release).  Would also allow us to stop needing Questionable.  */
+   view it is a mistake to do this separately from Entries, I dunno.  */
 
 enum base_walk
 {




reply via email to

[Prev in Thread] Current Thread [Next in Thread]