Take a pointer to the relevant entry of the command table in the client structure. This is generally a more sounding design, simplifies a few functions prototype, and as a side effect fixes a bug related to the conversion of EXPIRE -1 to DEL: before of this fix Redis tried to convert it into an EXPIREAT in the AOF code, regardless of our rewrite of the command.

don't process EXPIRE with negative TTL or EXPIREAT with time in the past if we are a slave too (see http://groups.google.com/group/redis-db/browse_thread/thread/5a931fefb88b16d5). Also propagate it as DEL.

They will be expired (and a DEL will be logged) after the loading is done
instead.

Fixed a problem with AOF when it is stopped via CONFIG SET appendonly no. We used to kill the wrong child...

childrens -> children in INFO output field names. This is a backward incompatible change, but really a minimal one.

Partial fix for a problem with AOF and BRPOP. We have at least a single evidence of an AOF that ended with a BRPOP call against an empty list, causing later issues at run time. Now the problem is detected while loading the AOF at startup, even if it is still to understand how the corrupted AOF was generated.

Use a safe iterator while saving the DB, since the getExpire() function will access the iterating dictionary.

AOF log rewriting in slave performed after a successful sych with the master was misplaced. Now it happens at the right time.

Fix for issue 516, rewriting the command vector to correctly repliate BRPOPLPUSH. Still to test everything, especially edge cases

Fix for Pub/Sub system, introduced in Redis 2.2.6 with the new copy-on-write safe iterator semantics. In the hope this is the last bug I introduced this way.