Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #2790

Closed
Open
Created 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 an admin enable hashed storage. More information
Assignee
Assign to
Time tracking