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 | 89a2528b1cc697c9ab2f6bfc282d9d5c0ed7cf87 (patch) | |
| tree | 3b88f23c76de7bdb2f7a885f4d87deff7eee1990 /proposals/001-process.txt | |
| parent | b08890be1559716601cb0170aeb7c3bb354e7e85 (diff) | |
| download | torspec-89a2528b1cc697c9ab2f6bfc282d9d5c0ed7cf87.tar.gz torspec-89a2528b1cc697c9ab2f6bfc282d9d5c0ed7cf87.zip | |
Clarify that implementation is for discussion of implementation
Diffstat (limited to 'proposals/001-process.txt')
| -rw-r--r-- | proposals/001-process.txt | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/proposals/001-process.txt b/proposals/001-process.txt index 636ba2c..e2fe358 100644 --- a/proposals/001-process.txt +++ b/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 |