1. 23 Apr, 2018 17 commits
  2. 01 Mar, 2018 1 commit
  3. 27 Feb, 2018 1 commit
  4. 13 Dec, 2017 1 commit
  5. 01 Dec, 2017 1 commit
  6. 27 Nov, 2017 2 commits
  7. 03 Aug, 2017 1 commit
  8. 26 Jul, 2017 2 commits
  9. 30 Jun, 2017 1 commit
    • antirez's avatar
      redis-cli --latency: ability to run non interactively. · 26e638a8
      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.
      26e638a8
  10. 15 May, 2017 1 commit
  11. 08 Jan, 2017 1 commit
  12. 12 Dec, 2016 1 commit
  13. 03 Dec, 2016 1 commit
  14. 02 Nov, 2016 1 commit
  15. 28 Oct, 2016 1 commit
  16. 13 Oct, 2016 1 commit
  17. 19 Sep, 2016 1 commit
  18. 16 Sep, 2016 2 commits
  19. 18 Jul, 2016 2 commits
  20. 05 Jul, 2016 1 commit
    • antirez's avatar
      redis-cli: check SELECT reply type just in state updated. · ef6a4df2
      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.
      ef6a4df2