- 25 Jun, 2013 3 commits
- 19 Jun, 2013 2 commits
- 12 Jun, 2013 1 commit
-
-
Marc-Antoine Perennou authored
Signed-off-by:
Marc-Antoine Perennou <Marc-Antoine@Perennou.com>
-
- 31 May, 2013 1 commit
-
-
antirez authored
-
- 30 May, 2013 2 commits
- 15 May, 2013 1 commit
-
-
antirez authored
Required because of recent changes in the way logfile is set to standard output.
-
- 09 May, 2013 1 commit
-
-
antirez authored
-
- 08 May, 2013 2 commits
- 23 Apr, 2013 1 commit
-
-
antirez authored
When the test is executed using the root account, setting the permission to 222 does not work as expected, as root can read files with 222 permission. Now we skip the test if root is detected. This fixes issue #1034 and the duplicated #1040 issue. Thanks to Jan-Erik Rediger (@badboy on Github) for finding a way to reproduce the issue.
-
- 22 Apr, 2013 1 commit
-
-
antirez authored
-
- 04 Apr, 2013 1 commit
-
-
antirez authored
-
- 28 Mar, 2013 3 commits
- 27 Mar, 2013 3 commits
- 25 Mar, 2013 1 commit
-
-
antirez authored
Fixes #621.
-
- 13 Mar, 2013 2 commits
- 12 Mar, 2013 1 commit
-
-
antirez authored
-
- 12 Feb, 2013 2 commits
- 05 Feb, 2013 1 commit
-
-
antirez authored
-
- 28 Jan, 2013 4 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
When keyspace events are enabled, the overhead is not sever but noticeable, so this commit introduces the ability to select subclasses of events in order to avoid to generate events the user is not interested in. The events can be selected using redis.conf or CONFIG SET / GET.
-
antirez authored
-
- 23 Jan, 2013 2 commits
-
-
Johan Bergström authored
-
Johan Bergström authored
-
- 21 Jan, 2013 1 commit
-
-
antirez authored
UNSUBSCRIBE and PUNSUBSCRIBE commands are designed to mass-unsubscribe the client respectively all the channels and patters if called without arguments. However when these functions are called without arguments, but there are no channels or patters we are subscribed to, the old behavior was to don't reply at all. This behavior is broken, as every command should always reply. Also it is possible that we are no longer subscribed to a channels but we are subscribed to patters or the other way around, and the client should be notified with the correct number of subscriptions. Also it is not pretty that sometimes we did not receive a reply at all in a redis-cli session from these commands, blocking redis-cli trying to read the reply. This fixes issue #714.
-
- 19 Jan, 2013 2 commits
- 15 Jan, 2013 1 commit
-
-
antirez authored
-
- 10 Jan, 2013 1 commit
-
-
antirez authored
-