- 23 Nov, 2010 1 commit
-
-
Pieter Noordhuis authored
-
- 22 Nov, 2010 10 commits
-
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Ryan Tecco authored
void*
-
Ryan Tecco authored
-
- 19 Nov, 2010 2 commits
-
-
Pieter Noordhuis authored
This causes non-deterministic error messages because sometimes the socket will already be closed and sometimes it is yet to be closed.
-
Ryan Tecco authored
-
- 15 Nov, 2010 3 commits
-
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
- 05 Nov, 2010 1 commit
-
-
Pieter Noordhuis authored
-
- 04 Nov, 2010 5 commits
-
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
- 03 Nov, 2010 9 commits
-
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
- 02 Nov, 2010 7 commits
-
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
When there is an I/O error, errno should be used to find out what is wrong. In other cases, errno cannot be used. So, use an explicit type in Hiredis to define the different error scenarios that can occur.
-
Pieter Noordhuis authored
-
- 01 Nov, 2010 2 commits
-
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-