diff options
author | Kaige Ye <yekaige2010@gmail.com> | 2023-03-15 17:05:42 +0800 |
---|---|---|
committer | GitHub <noreply@github.com> | 2023-03-15 11:05:42 +0200 |
commit | 5360350e4aeaa2c7498be4af29aee449f0ee49ad (patch) | |
tree | cea49737c24b6d2d8d2d0997f55453892c6994be /src/replication.c | |
parent | 9344f654c6227f30adf8bafd49b4218357c438b7 (diff) | |
download | redis-5360350e4aeaa2c7498be4af29aee449f0ee49ad.tar.gz |
cleanup NBSP characters in comments (#10555)
Replace NBSP character (0xC2 0xA0) with space (0x20).
Looks like that was originally added due to misconfigured editor which seems to have been fixed by now.
Diffstat (limited to 'src/replication.c')
-rw-r--r-- | src/replication.c | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/src/replication.c b/src/replication.c index 14f32a869..0e575111b 100644 --- a/src/replication.c +++ b/src/replication.c @@ -1764,16 +1764,16 @@ void replicationCreateMasterClient(connection *conn, int dbid) { connSetReadHandler(server.master->conn, readQueryFromClient); /** - * Important note: - * The CLIENT_DENY_BLOCKING flag is not, and should not, be set here. - * For commands like BLPOP, it makes no sense to block the master - * connection, and such blocking attempt will probably cause deadlock and - * break the replication. We consider such a thing as a bug because - * commands as BLPOP should never be sent on the replication link. - * A possible use-case for blocking the replication link is if a module wants - * to pass the execution to a background thread and unblock after the - * execution is done. This is the reason why we allow blocking the replication - * connection. */ + * Important note: + * The CLIENT_DENY_BLOCKING flag is not, and should not, be set here. + * For commands like BLPOP, it makes no sense to block the master + * connection, and such blocking attempt will probably cause deadlock and + * break the replication. We consider such a thing as a bug because + * commands as BLPOP should never be sent on the replication link. + * A possible use-case for blocking the replication link is if a module wants + * to pass the execution to a background thread and unblock after the + * execution is done. This is the reason why we allow blocking the replication + * connection. */ server.master->flags |= CLIENT_MASTER; server.master->authenticated = 1; |