[or-cvs] r8808: clarify recent spec stuff (in tor/trunk: . doc)

[nickm at seul.org]

Author: nickm
Date: 2006-10-23 16:17:04 -0400 (Mon, 23 Oct 2006)
New Revision: 8808

Modified:
   tor/trunk/
   tor/trunk/doc/control-spec.txt
   tor/trunk/doc/version-spec.txt
Log:
 r9358 at Kushana:  nickm | 2006-10-23 12:02:25 -0400
 clarify recent spec stuff



Property changes on: tor/trunk
___________________________________________________________________
 svk:merge ticket from /tor/trunk [r9358] on c95137ef-5f19-0410-b913-86e773d04f59

Modified: tor/trunk/doc/control-spec.txt
===================================================================
--- tor/trunk/doc/control-spec.txt	2006-10-23 11:29:15 UTC (rev 8807)
+++ tor/trunk/doc/control-spec.txt	2006-10-23 20:17:04 UTC (rev 8808)
@@ -941,9 +941,8 @@
      Action is a string, and Arguments is a series of keyword=value
      pairs on the same line.
 
-     Controllers who listen to these events will be assumed to want
-     both EXTENDED_EVENTS and VERBOSE_NAMES; see the explanations
-     in the USEFEATURE section command for details.
+     These events are always produced with EXTENDED_EVENTS and VERBOSE_NAMES;
+     see the explanations in the USEFEATURE section command for details.
 
   Actions for STATUS_GENERAL severity NOTICE events can be as follows:
 

Modified: tor/trunk/doc/version-spec.txt
===================================================================
--- tor/trunk/doc/version-spec.txt	2006-10-23 11:29:15 UTC (rev 8807)
+++ tor/trunk/doc/version-spec.txt	2006-10-23 20:17:04 UTC (rev 8808)
@@ -32,9 +32,10 @@
 numbers. The status tag is purely informational, and lets you know how
 stable we think the release is: "alpha" is pretty unstable; "rc" is a
 release candidate; and no tag at all means that we have a final
-release. If the tag ends with "-cvs", you're looking at a development
-snapshot that came after a given release.  If we *do* encounter two
-versions that differ only by status tag, we compare them lexically.
+release. If the tag ends with "-cvs" or "-dev", you're looking at a
+development snapshot that came after a given release.  If we *do*
+encounter two versions that differ only by status tag, we compare them
+lexically.
 
 Now, we start each development branch with (say) 0.1.1.1-alpha.  The
 patchlevel increments consistently as the status tag changes, for