diff options
| author | Nick Mathewson <nickm@torproject.org> | 2010-08-03 14:25:07 -0400 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2010-08-03 14:25:07 -0400 |
| commit | cafd868a7898a0aac7eaf58f76a8e1180766d3a8 (patch) | |
| tree | f6581841f9b9570d1f0d68778ee7101b47ad4f5a /doc/spec | |
| parent | d5abd0b43ebf0a5436250533a610dbab47b0474b (diff) | |
| download | tor-cafd868a7898a0aac7eaf58f76a8e1180766d3a8.tar.gz tor-cafd868a7898a0aac7eaf58f76a8e1180766d3a8.zip | |
Clarify that implementation is for discussion of implementation
Diffstat (limited to 'doc/spec')
| -rw-r--r-- | 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 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 |