1. 07 Apr, 2017 3 commits
  2. 22 Mar, 2017 2 commits
  3. 23 Jan, 2017 1 commit
  4. 30 Dec, 2016 1 commit
  5. 09 Dec, 2016 3 commits
    • not-a-robot's avatar
      Auto merge of #429 - xinchuantao:master, r=badboy · 33152ad1
      not-a-robot authored
      using new version libevent
      33152ad1
    • not-a-robot's avatar
      Auto merge of #468 - paul-scott:master, r=badboy · b4f9fc1a
      not-a-robot authored
      Prevented uv adapter from calling write when context has been freed
      
      The `redisLibuvPoll` function can be called with both the `UV_READABLE` and `UV_WRITABLE` flags set at the same time.  Calling `redisAsyncHandleRead` can lead to a disconnect and the context being cleaned up/freed.  If this happens then `redisAsyncHandleWrite` should not be called otherwise memory read/write errors and duplicate freeing will occur.
      
      These changes prevent this from happening by having the `redisLibuvCleanup` callback indicate that the context has been cleaned.  This is done indirectly by setting the context to a null pointer, maybe someone can come up with a cleaner way.
      b4f9fc1a
    • Jan-Erik Rediger's avatar
      Avoid unchecked malloc · 8636d908
      Jan-Erik Rediger authored
      Closes #471
      8636d908
  6. 04 Nov, 2016 1 commit
  7. 25 Oct, 2016 1 commit
    • Donald Whyte's avatar
      Remove trailing comma in redisConnectionType enum · 41b07dab
      Donald Whyte authored
      Remove trailing comma in last value of `redisConnectionType` enum. This causes a compiler warning on Solaris compilers. I'd like to build this on Solaris with `-Werror`. However, due to the trailing comma, I cannot do that.
      
      This PR removes the trailing comma, which should prevent it causing compiler warnings on any architecture.
      41b07dab
  8. 09 Oct, 2016 1 commit
    • Trustfarm-heart's avatar
      Build error patch with glib-2.0 · 06eedd8a
      Trustfarm-heart authored
      In case of some glib-2.0 linker error ,
      make examples 
      can't link with glib2.0,  in this case -lglib-2.0  to after includes and move to last will solve the issues.
      06eedd8a
  9. 19 Sep, 2016 1 commit
  10. 09 Jul, 2016 1 commit
  11. 07 Jul, 2016 1 commit
  12. 20 Jun, 2016 7 commits
  13. 20 May, 2016 1 commit
  14. 14 May, 2016 3 commits
  15. 13 May, 2016 1 commit
  16. 12 May, 2016 1 commit
    • not-a-robot's avatar
      Auto merge of #378 - thomaslee:tom_fix_kfreebsd, r=badboy · e93c05a7
      not-a-robot authored
      Fix strerror_r on some esoteric platforms
      
      Defining _XOPEN_SOURCE=1 causes strange behavior on Debian kfreebsd archs -- i.e. the GNU userspace with FreeBSD kernel -- when _GNU_SOURCE is not defined (the default).
      
      Not sure I fully understand the bizarre semantics, but it seems to use the XSI-compliant interface (int strerror_r(int, char*, size_t)) but the GNU implementation (char *strerror_r(int, char*, size_t)) such that strerror_r returns 32-bits of a 64-bit char * on x86_64 kfreebsd. We would expect strerror_r to return zero when using the XSI-compliant strerror_r implementation or a 64-bit char* when using the GNU version. Instead, we get something in between!
      
      Unless I'm missing something, being more explicit about what version of _XOPEN_SOURCE we want seems to be the prudent thing to do here -- and if folks want the GNU implementation of strerror_r for some reason they can always -D_GNU_SOURCE explicitly.
      e93c05a7
  17. 20 Apr, 2016 11 commits