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

Replace usage of the term "spermy" with "optimistic". #76

Merged

Conversation

luisdelarosa
Copy link
Contributor

No description provided.

@alloy alloy self-assigned this Mar 30, 2014
@luisdelarosa
Copy link
Contributor Author

This should fix issue #74

@joshkalpin
Copy link
Member

It looks ok on my end. I'd like @alloy or @irrationalfab to take a look on the basis that I have no idea if this got all of it.

@orta
Copy link
Member

orta commented Mar 30, 2014

👍

@fabiopelosin
Copy link
Member

What is the term that we should use? optimistic or approximate operator?

@orta
Copy link
Member

orta commented Mar 30, 2014

personally, optimistic

@fabiopelosin
Copy link
Member

me too!

@joshkalpin
Copy link
Member

optimistic sounds happier so I'll give it a 👍

@luisdelarosa luisdelarosa changed the title Replace usage of the term "spermy" with "approximate". Replace usage of the term "spermy" with "optimistic". Mar 30, 2014
@luisdelarosa
Copy link
Contributor Author

Changed it to "optimistic" and added a commit to my pull request which should fix this issue.

@fabiopelosin
Copy link
Member

Looks great! Thanks 👯

fabiopelosin added a commit that referenced this pull request Mar 30, 2014
Replace usage of the term "spermy" with "optimistic".
@fabiopelosin fabiopelosin merged commit 4a563ad into CocoaPods:master Mar 30, 2014
@orta
Copy link
Member

orta commented Mar 30, 2014

🐻

Ashton-W pushed a commit to Ashton-W/Core that referenced this pull request Nov 2, 2015
…_operator

Replace usage of the term "spermy" with "optimistic".
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 this pull request may close these issues.

5 participants