#27167: track "first" OR_CONN -------------------------------------------------+------------------------- Reporter: catalyst | Owner: | catalyst Type: enhancement | Status: | merge_ready Priority: Medium | Milestone: Tor: | 0.4.0.x-final Component: Core Tor/Tor | Version: Severity: Normal | Resolution: Keywords: usability, ux, ux-team, bootstrap, | Actual Points: 035-roadmap-subtask, 035-triaged-in-20180711, | s8-bootstrap, 035-deferred-20180930, | s8-errors | Parent ID: #27103 | Points: Reviewer: nickm | Sponsor: | Sponsor8 -------------------------------------------------+------------------------- Changes (by nickm):
* status: needs_review => merge_ready Comment: This is looking solid; I don't have any must-change items. I have left a couple of questions on the PR, to make sure I understand what's going on. One more general question: Do you think that eventually all calls to control_event_bootstrap() should come from the btrack subsystem, or do you think that the ones that remain outside it are unproblematic? Two requests: 1. Could you please open a ticket to deal with the PT issue? 2. When I merge this later today, could you please close the tickets that are fixed by it? -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/27167#comment:11> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs