gzz-commits
[Top][All Lists]
Advanced

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

[Gzz-commits] manuscripts/storm article.rst


From: Benja Fallenstein
Subject: [Gzz-commits] manuscripts/storm article.rst
Date: Sat, 15 Feb 2003 12:27:55 -0500

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Benja Fallenstein <address@hidden>      03/02/15 12:27:55

Modified files:
        storm          : article.rst 

Log message:
        comment out zone issue

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/storm/article.rst.diff?tr1=1.183&tr2=1.184&r1=text&r2=text

Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.183 manuscripts/storm/article.rst:1.184
--- manuscripts/storm/article.rst:1.183 Sat Feb 15 12:23:19 2003
+++ manuscripts/storm/article.rst       Sat Feb 15 12:27:55 2003
@@ -1116,10 +1116,12 @@
 
 Besides these issues with the backend, we are facing user interface issues
 as well -- for example the conventions for listing, moving and deleting
-blocks. Also conventions for which zones e.g. new blocks should be stored in
-must be resolved. Often they will be private, but when making changes to
-documents that are shared with a project group, the changes should be
-visible to others.
+blocks. 
+
+.. Also conventions for which zones e.g. new blocks should be stored in
+   must be resolved. Often they will be private, but when making changes to
+   documents that are shared with a project group, the changes should be
+   visible to others.
 
 We have provided a case study in
 what's possible in a system that does not use




reply via email to

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