Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Assign # to keyid flexibility TAP? #114

Closed
brainwane opened this issue May 12, 2020 · 2 comments · Fixed by #115
Closed

Assign # to keyid flexibility TAP? #114

brainwane opened this issue May 12, 2020 · 2 comments · Fixed by #115

Comments

@brainwane
Copy link

Now that #112 has been merged, should candidate-keyid-tap.md get a number and go into the list/index in the README?
@jhdalek55
Copy link
Contributor

jhdalek55 commented May 12, 2020 •
edited
Loading

I second this. It would make it easier to find, thus better facilitating discussion.

@mnm678
Copy link
Contributor

mnm678 commented May 12, 2020

Yes, I will submit a pr to add a TAP number in accordance with TAP 1.

@mnm678 mnm678 mentioned this issue May 12, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Assign a TAP number to candidate-keyid-tap mnm678/taps
3 participants
@brainwane @mnm678 @jhdalek55