src/fmacros.h | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 fix-ftbfs-on-kfreebsd

deps/linenoise/Makefile | 2 1 + 1 - 0 !
src/Makefile | 2 1 + 1 - 0 !
2 files changed, 2 insertions(+), 2 deletions(-)

 add cppflags in upstream makefiles

redis.conf | 15 9 + 6 - 0 !
sentinel.conf | 9 5 + 4 - 0 !
2 files changed, 14 insertions(+), 10 deletions(-)

 set debian configuration defaults.

src/aof.c | 4 2 + 2 - 0 !
src/rdb.c | 7 4 + 3 - 0 !
2 files changed, 6 insertions(+), 5 deletions(-)

 use get_current_dir_name over pathmax, etc.

deps/Makefile | 2 2 + 0 - 0 !
src/Makefile | 5 5 + 0 - 0 !
src/debug.c | 4 4 + 0 - 0 !
src/object.c | 5 5 + 0 - 0 !
src/zmalloc.c | 10 10 + 0 - 0 !
src/zmalloc.h | 4 4 + 0 - 0 !
6 files changed, 30 insertions(+)

 add support for use_system_jemalloc flag.

https://github.com/antirez/redis/pull/5279

deps/Makefile | 2 2 + 0 - 0 !
src/Makefile | 15 12 + 3 - 0 !
2 files changed, 14 insertions(+), 3 deletions(-)

 add support for a use_system_lua flag.

deps/Makefile | 2 2 + 0 - 0 !
src/Makefile | 19 14 + 5 - 0 !
2 files changed, 16 insertions(+), 5 deletions(-)

 add support for a use_system_hiredis flag.

src/scripting.c | 1 1 + 0 - 0 !
1 file changed, 1 insertion(+)

 ensure we use the modules for third-party libraries.

src/replication.c | 6 2 + 4 - 0 !
src/server.c | 4 2 + 2 - 0 !
2 files changed, 4 insertions(+), 6 deletions(-)

 send the readiness notification when we are ready to accept
 connections

On a replica we do accept connections, even though commands accessing
the database will operate in read-only mode. But the server is still
already operational and processing commands.

Not sending the readiness notification means that on a HA setup where
the nodes all start as replicas (with replicaof in the config) with
a replica that cannot connect to the master server and which might not
come back in a predictable amount of time or at all, the service
supervisor will end up timing out the service and terminating it, with
no option to promote it to be the main instance. This seems counter to
what the readiness notification is supposed to be signaling.

Instead send the readiness notification when we start accepting
commands, and then send the various server status changes as that.

Fixes: commit 641c64ada10404356fc76c0b56a69b32c76f253c
Fixes: commit dfb598cf3304818e608ceb6b5d9529a293345c4a

Ref: Debian:#981226
Ref: <https://github.com/redis/redis/pull/8409>