[tor-commits] [torspec/master] Don't enumerate event types in section 3.4

[nickm@xxxxxxxxxxxxxx]

commit 4b674a721d984a6390773f95b87f42eb82067b40
Author: Damian Johnson <atagar@xxxxxxxxxxxxxx>
Date:   Sun Nov 3 10:06:53 2013 -0800

    Don't enumerate event types in section 3.4
    
    When adding an event type we expect spec authors to edit both section 3.4 and
    4.1.x. This is error prone...
    
      https://trac.torproject.org/10085
    
    Dropping the redundant listing of event types and simply citing 4.1.x.
---
 control-spec.txt |    7 +------
 1 file changed, 1 insertion(+), 6 deletions(-)

diff --git a/control-spec.txt b/control-spec.txt
index f84d078..9227302 100644
--- a/control-spec.txt
+++ b/control-spec.txt
@@ -296,12 +296,7 @@
 
      "SETEVENTS" [SP "EXTENDED"] *(SP EventCode) CRLF
 
-     EventCode = "CIRC" / "STREAM" / "ORCONN" / "BW" / "DEBUG" /
-         "INFO" / "NOTICE" / "WARN" / "ERR" / "NEWDESC" / "ADDRMAP" /
-         "AUTHDIR_NEWDESCS" / "DESCCHANGED" / "STATUS_GENERAL" /
-         "STATUS_CLIENT" / "STATUS_SERVER" / "GUARD" / "NS" / "STREAM_BW" /
-         "CLIENTS_SEEN" / "NEWCONSENSUS" / "BUILDTIMEOUT_SET" / "SIGNAL" /
-         "CONF_CHANGED" / "CIRC_MINOR" / "TRANSPORT_LAUNCHED"
+     EventCode = 1*(ALPHA / "_")  (see section 4.1.x for event types)
 
   Any events *not* listed in the SETEVENTS line are turned off; thus, sending
   SETEVENTS with an empty body turns off all event reporting.



_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits