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
  • #29137

Closed (moved)
Open
Opened Jan 19, 2019 by Damian Johnson@atagar

Standardize 'Bandwidth File' name

Usually the 'Bandwidth File' spec called its actual documents 'Bandwidth Lists'. Juga and teor have both said they prefer the term 'Bandwidth File'. Standardizing this so we have a consistent name for these documents...

https://trac.torproject.org/projects/tor/ticket/28615#comment:9

Fix is available in the 'bandwidth_file_name' branch of my spec repo...

https://gitweb.torproject.org/user/atagar/torspec.git/commit/?h=bandwidth_file_name

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