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

Closed
Open
Opened Mar 23, 2011 by Tomas Touceda@chiiph

What Vidalia branches should be archived?

The git migration is about done, we are still checking if everything's ok.

There are a couple of branches from the svn repo that need to either get archived, or to get documentation about what they were trying to accomplish so we can revive them against the current status of the project.

Matt: What do you think? All of the branches are more than a year old, but may be the concepts behind them still apply and are worth keeping in mind.

Branches are: alt-launcher auto-updates breakpad domenikb exit-country extension-api hidden-services marble upnp

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