]> git.ipfire.org Git - thirdparty/tor.git/commitdiff
Clarify that implementation is for discussion of implementation
authorNick Mathewson <nickm@torproject.org>
Tue, 3 Aug 2010 18:25:07 +0000 (14:25 -0400)
committerNick Mathewson <nickm@torproject.org>
Tue, 3 Aug 2010 18:25:07 +0000 (14:25 -0400)
doc/spec/proposals/001-process.txt

index 636ba2c2fa8dca5ee70b605a3f63004a4fbb40ab..e2fe358fedbe7adbad236ffc86a78b72bab7037b 100644 (file)
@@ -127,7 +127,8 @@ What should go in a proposal:
 
       Implementation: If the proposal will be tricky to implement in Tor's
         current architecture, the document can contain some discussion of how
-        to go about making it work.
+        to go about making it work.  Actual patches should go on public git
+        branches, or be uploaded to trac.
 
       Performance and scalability notes: If the feature will have an effect
         on performance (in RAM, CPU, bandwidth) or scalability, there should