-
Notifications
You must be signed in to change notification settings - Fork 108
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
PR 53 reverts PR 46 #55
Comments
will investigate |
I will reapply #46 |
turns out our internal source repository was out of sync with GitHub repo. our mistake. sorry about that. |
Thanks for re-applying. Also thanks for fixing "occured" -- that one was driving me nuts but I didn't want to make that change in a totally unrelated PR. |
this has been fixed. 1.0.3 pushed to npm. |
ghost
closed this as completed
Jun 4, 2015
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#46 was merged into mainline, but the merge of #53 reverted those changes. Intentional, or bad merge conflict? #46 was a fix for #45, which is mentioned in the changelog for 1.0.2.
The text was updated successfully, but these errors were encountered: