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.

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

Misspelled COMANND #924

Closed
weaversa opened this issue Oct 1, 2020 · 4 comments · Fixed by #925
Closed

Misspelled COMANND #924

weaversa opened this issue Oct 1, 2020 · 4 comments · Fixed by #925

Comments

@weaversa
Copy link
Collaborator

weaversa commented Oct 1, 2020

cryptol/cry

Line 14 in eeadea1

Usage: $0 COMMAND COMANND_OPTIONS

@brianhuffman
Copy link
Contributor

brianhuffman commented Oct 1, 2020

I've actually been meaning to make a ticket thread to keep track of all the typos I find in the Cryptol repo, so I can batch the fixes together (it never seems worth the trouble to make a PR just to fix one typo). Here are some others that I know of:

@yav
Copy link
Member

yav commented Oct 1, 2020

I am proud to say that I probably made most of these :)
Why not just fix them in the code as you find them?

@brianhuffman
Copy link
Contributor

Because I'm usually in the middle of making a PR for something unrelated when I find them.

Actually, I'd guess that the "efficently" is Rob's; he's made that typo before in crucible and so I did git grep efficent just now and found it

brianhuffman pushed a commit that referenced this issue Oct 1, 2020
@brianhuffman brianhuffman linked a pull request Oct 1, 2020 that will close this issue
@brianhuffman
Copy link
Contributor

I just made a PR for all of those. Updating an issue thread is probably too much work to do in the future, so instead I'll just note typos locally when I find them and make PRs whenever it seems reasonable.

brianhuffman pushed a commit that referenced this issue Oct 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants