[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #1602 [Metrics]: TorStatus should use Tordnsel instead of its own

#1602: TorStatus should use Tordnsel instead of its own
----------------------------+-----------------------------------------------
        Reporter:  phobos   |        Owner:  karsten              
            Type:  task     |       Status:  reopened             
        Priority:  normal   |    Milestone:  Tor Status Deployment
       Component:  Metrics  |      Version:                       
      Resolution:           |     Keywords:                       
          Parent:           |       Points:                       
Actualpointsdone:           |   Pointsdone:                       
    Actualpoints:           |  
----------------------------+-----------------------------------------------
Changes (by arma):

  * status:  closed => reopened
  * resolution:  wontfix =>


Comment:

 Should we make a new torstatus component for these tickets? It seems silly
 to close a good bug report just because you have another piece of software
 that you're working on instead. Torstatus is the software that many users
 use right now, and we have known bugs on it. We should point volunteers at
 this set of bugs (among many other things).

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/1602#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs