From: Nick Mathewson Date: Tue, 3 Aug 2010 18:25:07 +0000 (-0400) Subject: Clarify that implementation is for discussion of implementation X-Git-Tag: tor-0.2.2.15-alpha~44 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=cafd868a7898a0aac7eaf58f76a8e1180766d3a8;p=thirdparty%2Ftor.git Clarify that implementation is for discussion of implementation --- diff --git a/doc/spec/proposals/001-process.txt b/doc/spec/proposals/001-process.txt index 636ba2c2fa..e2fe358fed 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