gzz-commits
[Top][All Lists]
Advanced

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

[Gzz-commits] journals hemppah


From: Hermanni Hyytiälä
Subject: [Gzz-commits] journals hemppah
Date: Fri, 06 Jun 2003 10:15:13 -0400

CVSROOT:        /cvsroot/fenfire
Module name:    journals
Branch:         
Changes by:     Hermanni Hyytiälä <address@hidden>      03/06/06 10:15:13

Modified files:
        .              : hemppah 

Log message:
        this week

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/fenfire/journals/hemppah.diff?tr1=1.14&tr2=1.15&r1=text&r2=text

Patches:
Index: journals/hemppah
diff -u journals/hemppah:1.14 journals/hemppah:1.15
--- journals/hemppah:1.14       Fri May 30 10:31:25 2003
+++ journals/hemppah    Fri Jun  6 10:15:13 2003
@@ -5,6 +5,17 @@
 Long term
 ---------
 
+2003-06-05 -
+
+    - Decentralized version control
+      - CVS-like behaviour      
+      - http://www.bitkeeper.com/
+      - http://www.wlug.org.nz/CVS
+      - http://www.cvshome.org      
+    - Version system with Storm pointers
+    - First: are DHTs/DSHTs suitable for our needs/version control
+      - Write a PEG document      
+
 2003-05-23 -
 
     - start thinking a simulation framework for Storm/P2P       
@@ -24,21 +35,28 @@
     
 2003-05-20 -
 
-    - start thining (initially) model for Gnutella/DHT integration
+    - start thinking (initially) model for Gnutella/DHT integration
       - first: is it possible ?
       - second: what are the tradeoffs ?    
     
 Short term
 ----------
 
-2003-06-03
-    - write a PEG about Storm/GISP simulation
-      - hypothesis and research problems/issues      
-
+2003-06-05 -     
+ 
+    - write a PEG about GISP "killer"
+    - started looking GISP code
+      - possibly implement the "killer" based
+        on native GISP's simulation code
 
 =============
 Past:
 =============
+
+2003-06-02 - 2003-06-05
+    - write a PEG about Storm/GISP simulation
+      - hypothesis and research problems/issues
+      - postponed
 
 2003-05-30
 




reply via email to

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