- 23 Apr, 2018 17 commits
-
-
Artix authored
-
artix authored
-
artix authored
parsing bug and other minor bugs.
-
artix authored
- Almost all Cluster Manager related code moved to the same section. - Many macroes converted to functions - Added various comments - Little code restyling
-
artix authored
- Code improvements
-
artix authored
-
artix authored
-
artix authored
-
artix authored
-
artix authored
-
artix authored
-
artix authored
-
artix authored
-
artix authored
- Cluster Manager: fixed flags assignment in clusterManagerNodeLoadInfo
-
artix authored
-
artix authored
-
artix authored
-
- 01 Mar, 2018 1 commit
-
-
antirez authored
-
- 27 Feb, 2018 1 commit
-
-
charsyam authored
-
- 13 Dec, 2017 1 commit
-
-
Tomasz Poradowski authored
- when redis-cli is running in a TTY - always enable command history buffering, regardless if history file path can be successfully determined
-
- 01 Dec, 2017 1 commit
-
-
antirez authored
-
- 27 Nov, 2017 2 commits
-
-
zhaozhao.zz authored
-
Itamar Haber authored
-
- 03 Aug, 2017 1 commit
-
-
jybaek authored
-
- 26 Jul, 2017 2 commits
-
-
Bo Cai authored
Signed-off-by:
Bo Cai <charpty@gmail.com>
-
Bo Cai authored
Signed-off-by:
Bo Cai <charpty@gmail.com>
-
- 30 Jun, 2017 1 commit
-
-
antirez authored
This feature was proposed by @rosmo in PR #2643 and later redesigned in order to fit better with the other options for non-interactive modes of redis-cli. The idea is basically to allow to collect latency information in scripts, cron jobs or whateever, just running for a limited time and then producing a single output.
-
- 15 May, 2017 1 commit
-
-
antirez authored
Close #3993.
-
- 08 Jan, 2017 1 commit
-
-
Jan-Erik Rediger authored
-
- 12 Dec, 2016 1 commit
-
-
Yossi Gottlieb authored
This happens if the server (mysteriously) returns an unexpected response to the COMMAND command.
-
- 03 Dec, 2016 1 commit
-
-
cbgbt authored
-
- 02 Nov, 2016 1 commit
-
-
antirez authored
Thanks to @qiaodaimadelaowang for signaling the issue. Close #3585.
-
- 28 Oct, 2016 1 commit
-
-
jybaek authored
-
- 13 Oct, 2016 1 commit
-
-
jybaek authored
-
- 19 Sep, 2016 1 commit
-
-
antirez authored
It was changed in Redis but not in redis-cli. Thanks to @oranagra for signaling.
-
- 16 Sep, 2016 2 commits
- 18 Jul, 2016 2 commits
- 05 Jul, 2016 1 commit
-
-
antirez authored
In issues #3361 / #3365 a problem was reported / fixed with redis-cli not updating correctly the current DB on error after SELECT. In theory this bug was fixed in 0042fb0e, but actually the commit only fixed the prompt updating, not the fact the state was set in a wrong way. This commit removes the check in the prompt update, now that hopefully it is the state that is correct, there is no longer need for this check.
-