Added a test case for an issue that resulted in STOREing a SORT with
multiple GETs fails.
A fix for an issue the prevented STOREing SORTs that contained multiple
GETs.

When using multiple GETs, Redis#sort expects the return to be an array.
However, combined with a STORE clause, the SORT will return an integer
representing the number of keys stored in the STORE list. The fix checks
if the reply from the Redis client is an integer, and if it is, it does
not attempt to process it as an array.
Minor refactoring to give some context to the code
Refactored to remain closer to original method
Merge pull request #328 from adammulligan/master

Sorting with multiple GETs fails to STORE
Make Future respond_to :class and :is_a? so that code given a potentially futuristic value from Redis can figure out if it is a Future or not.
Merge pull request #330 from hornairs/identifiable_futures

Make Futures identifiable
Ensure #watch returns OK without a block
Merge pull request #332 from ximus/master

Ensure #watch without a block returns "OK"
Update CHANGELOG
Bump patch
Update CHANGELOG
allow using a custom HashRing
Merge pull request #335 from nilsonsfj/master

Allows using a custom HashRing in Redis::Distributed
Added support for SET with EX, PX, NX, XX options.

Redis >= 2.6.12 adds options for setting timeouts and locks on keys.
http://redis.io/commands/set
Merge pull request #343 from benubois/set_options

Added support for SET with EX, PX, NX, XX options.
Update CHANGELOG
Add support for MIGRATE
Redis#inspect should call #id on original client
Whitespace