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.

removed assert causing an illegal memory access. This was responsible of crashes during BLPOP and other list blocking operations.

Introduced a safe iterator interface that can be used to iterate while accessing the dictionary at the same time. Now the default interface is consireded unsafe and should be used only with dictNext()

when Redis fails accepting a new connection reports the error at WARNING and not VERBOSE error level. Thanks to offby1 for proposing this in the Redis mailing list. #backport-candidate

Fixed a bug with replication where SLAVEOF NO ONE caused a slave to close the connection with its slaves