mirrors/tor
1
0
Fork 0
mirror of https://gitlab.torproject.org/tpo/core/tor.git synced 2024-11-20 02:09:24 +01:00
Code Issues Projects Releases Wiki Activity

r9358@Kushana: nickm | 2006-10-23 12:02:25 -0400

Browse Source 
clarify recent spec stuff


svn:r8808
This commit is contained in:
Nick Mathewson 2006-10-23 20:17:04 +00:00
parent 4665e1d18c
commit fbe3c803f2
2 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/control-spec.txt
View File

@ -941,9 +941,8 @@ $Id$
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:

7
doc/version-spec.txt
View File

@ -32,9 +32,10 @@ All versions should be distinguishable purely by those four
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