gzz-commits
[Top][All Lists]
Advanced

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

[Gzz-commits] journals benja


From: Benja Fallenstein
Subject: [Gzz-commits] journals benja
Date: Sun, 25 May 2003 13:05:26 -0400

CVSROOT:        /cvsroot/fenfire
Module name:    journals
Changes by:     Benja Fallenstein <address@hidden>      03/05/25 13:05:26

Modified files:
        .              : benja 

Log message:
        more thinking while off-line

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

Patches:
Index: journals/benja
diff -u journals/benja:1.51 journals/benja:1.52
--- journals/benja:1.51 Sun May 25 11:14:47 2003
+++ journals/benja      Sun May 25 13:05:26 2003
@@ -44,7 +44,7 @@
 Past:
 -----
 
-2003-05-25 [3.5h, 13.30-14.15, 14.30-17.15]:
+2003-05-25 [3.5h, 13.30-14.15, 14.30-19.00]:
 
 - think about article
 - integrate Storm with Emacs, so that clicking a text/plain
@@ -54,6 +54,20 @@
   versioning, with only storing diffs and with merging
   after concurrent edits on two different computers,
   and then we're talking ;-)
+- more thinking about pointers: creating a pointer scheme
+  we can make the persistency commitment on is extraordinarily
+  difficult. can we somehow protect a document so that
+  old versions are still retrievable after a key has been
+  revoked? -- if we had timestamping, one approach may be
+  that when the key for a document is revoked, the document
+  is frozen: all the old versions can still be retrieved,
+  but the document cannot be updated. but that, again,
+  needs timestamping...
+- an idea that may actually work: integrate the Storm stuff
+  with ReST: edit as reStructuredText, browse as HTML.
+  This could give us versioning *and* browsing, the latter
+  being important when going beyond a single system.
+  Needs thinking about how to integrate this well w/ pointers.
 
 2003-05-24 [8h, 13.45-17.00, 19.30-19.45, 20.00-0.00]:
 




reply via email to

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