aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorSebastian Hahn <sebastian@torproject.org>2009-05-05 15:48:23 +0200
committerSebastian Hahn <sebastian@torproject.org>2009-05-05 17:05:45 +0200
commitd0cb5e5b0bfa55ac7e3ec4f28cdea309aaeefd51 (patch)
treed4ddb37bc8919033f5974f52e26c679aafb1b396 /doc
parentdf8a47464a4e9adf30757a378ddb1f8aa317dbfa (diff)
downloadtor-d0cb5e5b0bfa55ac7e3ec4f28cdea309aaeefd51.tar.gz
tor-d0cb5e5b0bfa55ac7e3ec4f28cdea309aaeefd51.zip
SVN-specific metadata should no longer be part of a proposal
Update the proposal creation instructions to remove the Version and Last-Modified fields.
Diffstat (limited to 'doc')
-rw-r--r--doc/spec/proposals/001-process.txt6
1 files changed, 2 insertions, 4 deletions
diff --git a/doc/spec/proposals/001-process.txt b/doc/spec/proposals/001-process.txt
index 3a767b5fa4..5c12d01648 100644
--- a/doc/spec/proposals/001-process.txt
+++ b/doc/spec/proposals/001-process.txt
@@ -47,7 +47,7 @@ How to change the specs now:
Like an RFC, every proposal gets a number. Unlike RFCs, proposals can
change over time and keep the same number, until they are finally
accepted or rejected. The history for each proposal
- will be stored in the Tor Subversion repository.
+ will be stored in the Tor repository.
Once a proposal is in the repository, we should discuss and improve it
until we've reached consensus that it's a good idea, and that it's
@@ -82,9 +82,7 @@ How new proposals get added:
What should go in a proposal:
Every proposal should have a header containing these fields:
- Filename, Title, Version, Last-Modified, Author, Created, Status.
- The Version and Last-Modified fields should use the SVN Revision and Date
- tags respectively.
+ Filename, Title, Author, Created, Status.
These fields are optional but recommended:
Target, Implemented-In.