This repository has been archived by the owner on Apr 14, 2021. It is now read-only.
Remove sources of two outstanding warnings #2193
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Awesome! Thanks. This is a great candidate for the next 1.2 bugfix release. :) |
indirect
added a commit
that referenced
this pull request
Nov 30, 2012
Remove sources of two outstanding warnings
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bundler was
ruby -w-clean for a long time, until recently (1.2.0?) two warnings crept in. This is especially irritating when one runsrake specwith warnings on, to catch potential code issues in development.This pull request removes the sources of the two outstanding warnings and is against the
1-2-stablebranch. Let me know if it should be againstmaster(but it would be great if it made it into 1.2.x).