mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2024-11-20 10:12:15 +01:00
SVN-specific metadata should no longer be part of a proposal
Update the proposal creation instructions to remove the Version and Last-Modified fields.
This commit is contained in:
parent
df8a47464a
commit
d0cb5e5b0b
@ -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.
|
||||
|
Loading…
Reference in New Issue
Block a user