Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #7334

Closed (moved)
Open
Opened Nov 05, 2012 by Roger Dingledine@arma

tor-spec.txt says it only applies to tor 0.2.1.x

tor-spec.txt starts with

Note: This document aims to specify Tor as implemented in 0.2.1.x.  Future
versions of Tor may implement improved protocols, and compatibility is not
guaranteed.

I think tor-spec captures 0.2.2.x and 0.2.3.x as well as this point.

Should we just name those two branches too? If so, we're going to forget to add 0.2.4 when the time comes. We should think of a more future-proofy approach.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Tor: unspecified
Milestone
Tor: unspecified
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#7334