Add ExcludeDirectDirectoryFetchNodes option

changed milestone to %Tor: unspecified

added component::core tor/tor milestone::Tor: unspecified priority::medium resolution::wontfix severity::normal status::closed tor-client type::enhancement labels

Trac:
Keywords: N/A deleted, tor-client added

Trac:
Component: Tor Client to Tor

Trac:
Milestone: Tor: 0.2.4.x-final to Tor: 0.2.5.x-final

See also #5903 (moved), which is not quite the same, but which should be designed in tandem.

Trac:
Milestone: Tor: 0.2.5.x-final to Tor: 0.2.???

Milestone renamed

Trac:
Milestone: Tor: 0.2.??? to Tor: 0.3.???

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

Trac:
Milestone: Tor: 0.3.??? to Tor: unspecified
Keywords: N/A deleted, tor-03-unspecified-201612 added

What's the use case for this?

Especially in the new world where you fetch directory stuff from your guards.

I'm tempted to close, especially if we're leaving #5903 (moved) open.

Trac:
Severity: N/A to Normal
Reviewer: N/A to N/A
Sponsor: N/A to N/A

Remove an old triaging keyword.

Trac:
Keywords: tor-03-unspecified-201612 deleted, N/A added

Trac:
Status: new to closed
Resolution: N/A to wontfix

closed

moved to tpo/core/tor#6525 (closed)