Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • 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
  • #9971
Closed (moved) (moved)
Open
Created Oct 12, 2013 by Roger Dingledine@arma

for_discovery option in add_an_entry_guard() is confusingly named

In #9946 (moved) I added a new argument "for_discovery" to add_an_entry_guard(). Nick prefers "provisional" or "probationary".

In parallel, I think we should probably rename the made_contact field in entry guard t, to be why we're remembering that we've made contact, rather than simply that we have.

And lastly, we should do something about the godawful number of int arguments that add_an_entry_guard() now takes.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking