Fossil: Diff

Differences From:

File todo.txt part of check-in [81ccb7e684] - Removed two entries from the work list which are done. by aku on 2007-08-31 01:31:13. [view]
To:

File todo.txt part of check-in [b8cc22ebdf] - Merged dhr's todo and ideas update by jnc on 2007-09-24 23:56:25. Also file todo.txt part of check-in [d0305b305a] - Merged mainline into my branch to get the newest application. by aku on 2007-12-05 08:07:46. [view]
@@ -1,4 +1,31 @@
+Bugs:
+
+ *  When doing an update, if a file is not found that should be there
+    then the update aborts, only after it has written several files. It
+    does not update your checked out version, thus when doing a fossil
+    changes, you see everything that has come over from your update
+    command. Steps to reproduce:
+
+    $ rm src/main.c
+    $ fossil update 9b30
+    UPDATE ... etc ...
+    fossil: no such file: src/main.c
+    $ fossil info
+    (shows version you were on prior to update)
+    $ fossil changes
+    EDITED ... many ...
+
+ *  Bug: If the server closes the socket unexpectedly, the
+    fwrite() in http.c:103 throws a signal and kills the child
+    process.  fwrite() is not suppose to do this.  Need to figure
+    out what is going wrong.
+
+ *  Bug: Make sure merge and other commands (check-out) do not try
+    to use a phantom.
+
+ *  Bug: When clone use incorrect http URL, local repo file is still created.
+
 Things to work on:
 
  *  Use the wiki_convert() routine to render comments and other text
     on web pages.
@@ -12,23 +39,13 @@
  *  If the server returns an error (for example if the outbound /xfer
     message exceeds the maximum POST size of the server) the client
     does not report this error back to the user as it should.
 
- *  Bug: If the server closes the socket unexpectedly, the
-    fwrite() in http.c:103 throws a signal and kills the child
-    process.  fwrite() is not suppose to do this.  Need to figure
-    out what is going wrong.
-
- *  Bug: pull is ending prematurely.
-
- *  Bug: Make sure merge and other commands (check-out) do not try
-    to use a phantom.
-ż
  *  The ipaddr field of the rcvfrom table is not being set.  This
     field should be the IP address from which information is received
     for the local repository.  So when somebody does a push of new
     files we record the ipaddr.  Or when we do a pull, we record
-    the ipaddr.
+    the ipaddr.  (I think this has been fixed.  Need to test.)
 
  *  Additional information displayed for the "vinfo" page:
 
      +  All leaves of this version that are not included in the
@@ -37,21 +54,12 @@
         See the compute_leaves() function to see how to find all
         leaves.
      +  Add file diff links to the file change list.
 
- *  Timeline enhanced so that you can specify a range of dates.
-
- *  The /xfer handler (for push, pull, and clone) does not do
-    delta compression.  This results in excess bandwidth usage.
-    There are some pieces in xfer.c that are sketches of ideas on
-    how to do delta compression, but nothing has been implemented.
-
  *  Enhancements to the diff and tkdiff commands in the cli.
     Allow the entire tree or a subtree to be diffed, not just a
     single file.  Allow diffs against any two arbitrary versions,
-    not just diffs against the current check-out.  Allow
-    configuration options to replace tkdiff with some other
-    visual differ of the users choice. Example: eskil.
+    not just diffs against the current check-out.
 
  *  Ticketing interface (expand this bullet)
 
      +  Create new tickets as files in the file hierarchy
@@ -116,10 +124,11 @@
     a check-in comment with a new comment.  Comment changes should be
     GPG clearsigned at the very least.  Comment changes only apply if
     the user who made the change has the right permissions.
 
- *  Get a build working for win32.  Perhaps use cygwin.  Or omit
-    the server component from win32 (to eliminate the need for fork()).
-
  *  Make the interface to fossil look pretty and be customizable so
     that other people will be attracted to it, will take over maintenance
     of it, and we can eventually move on to other things.
+
+    This has begun, but I wonder if we need to use a templating system for
+    full customization. If the CSS is done correctly, you can change 99.9%
+    of everything. See: http://www.csszengarden.com/