[or-cvs] [tor/master] Clarify that implementation is for discussion of implementation

[nickm at torproject.org]

Author: Nick Mathewson <nickm at torproject.org>
Date: Tue, 3 Aug 2010 14:25:07 -0400
Subject: Clarify that implementation is for discussion of implementation
Commit: cafd868a7898a0aac7eaf58f76a8e1180766d3a8

---
 doc/spec/proposals/001-process.txt |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/doc/spec/proposals/001-process.txt b/doc/spec/proposals/001-process.txt
index 636ba2c..e2fe358 100644
--- a/doc/spec/proposals/001-process.txt
+++ b/doc/spec/proposals/001-process.txt
@@ -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
-- 
1.7.1