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

Correct precent/percent misspelling #10

Merged
merged 1 commit into from Aug 12, 2014
Merged

Correct precent/percent misspelling #10

merged 1 commit into from Aug 12, 2014

Conversation

@zarvox
Copy link
Contributor

zarvox commented Aug 12, 2014

There appears to be a misspelling in most of the lossy_precent_decode_* functions. This commit fixes the function as well as the docs.

Renaming these might break code that depends on this misspelling, though. Is there a good way to make a smooth migration, or do we just fix things and assume that dependent code will sort itself out soon enough?

SimonSapin added a commit that referenced this pull request Aug 12, 2014
Correct precent/percent misspelling

[breaking-change]
@SimonSapin SimonSapin merged commit 9d0e089 into servo:master Aug 12, 2014
1 check passed
1 check passed
continuous-integration/travis-ci The Travis CI build passed
Details
@SimonSapin
Copy link
Member

SimonSapin commented Aug 12, 2014

Good catch, thanks!

I’ve taken the rustc convention of having [breaking-change] in the (merge) commit message to indicate this. At least as long as Rust itself is not backward-compatible, I don’t think we should refrain from fixing broken things.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants
You can’t perform that action at this time.