#32404: Add a CFLG_OBSOLETE flag, and handle it at the confvar layer
-------------------------------+-------------------------------------------
Reporter: teor | Owner: nickm
Type: defect | Status: assigned
Priority: Medium | Milestone: Tor: 0.4.3.x-final
Component: Core Tor/Tor | Version: Tor: 0.4.2.1-alpha
Severity: Normal | Keywords: network-team-roadmap-november
Actual Points: | Parent ID: #29211
Points: 1 | Reviewer:
Sponsor: |
Sponsor31-must |
-------------------------------+-------------------------------------------
Follow up to #32295 for 0.4.3.
nickm says:
My suggestion would be to change how OBSOLETE is implemented: it doesn't
really make sense as a type. Instead, there should be an "empty" type for
fields that can't be read or written, and a CFLG_OBSOLETE flag that causes
these warnings. The CFLG_OBSOLETE flag should be handled at the confvar
layer, I think.
This is a bug caused by sponsor 31, so it's a must-have.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/32404>
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
