Changing the signature of respond_to? to conform to the correct parameters
Add WATCH command
1.1.0
Added support for mapped_hmget with tests.
Testing redis 3.0.0 compatibility

* Added .gitignore for Gemfile.lock
* Moved development dependencies to gemspec
* Removed redis gem version
Merge tag 'v1.1.0'
Revert "Changing the signature of respond_to? to conform to the correct parameters"

This reverts commit 00b472ab083f680ea41e6ca1cb36fa88d973126b.
use Redis.current which is thread safe as the default Redis connection
add support for missing commands
If you override respond_to? you should conform to Object#respond_to?(command, includ_private=false)
Merge pull request #32 from hectcastro/redis-namespace

---

I noticed that a namespace was being applied to the top-level `mapped_hmset` key, but not to keys requested via `mapped_hmget`.  This is a patch to add a namespace to the top-level key of `mapped_hmget`.

Any alternate solutions or feedback are welcome – and thanks for Resque.
Merge pull request #39 from czarneckid/redis-namespace

---

Now that the redis gem is at 3.0.0, I wanted to test this using the latest release. This really just removes the version restriction on the redis gem so that you can use redis-namespace with the redis-3.0.0 gem.

* Added .gitignore for Gemfile.lock
* Moved development dependencies to gemspec
* Removed redis gem version

I tested redis-namespace using the following:

* redis-2.2.0 and Redis 2.4.13
* redis-2.2.0 and Redis 2.5.9 (what will be the Redis 2.6 release)
* redis-3.0.0 and Redis 2.4.13
* redis-3.0.0 and Redis 2.5.9

All of the specs pass under those configurations.
lock to ~> 3.0.0 of redis
add myself to authors, so people know who to talk to
1.2.0 \o/
setup file for travis
add changelog
Add missing commands and some Redis 2.6 commands
Add missing specs for Redis 2.6 commands
Move from comment to pending.