Lines Matching refs:not

8 MODERATE: Program an upgrade of the server, but it's not urgent.
24    a replication delay. This is not an actual problem since things work
60    This is not really a bug fix, but may allow to more easily detect that
77    It's not a critical bug: the effect is to, sometimes, don't report objects
82 And now the good news (not that bug fixes are not good...), that is, the
212  A string with 21 chars is not representable as a 64-bit integer.
260    change in the jemalloc configuration did not really survived when the
277 below. There are still reported bugs for 3.2 that were not fixed in this
279 so likely a new release will not be too far.
359 opcodes, not the values itself as it happens in the case of RESTORE.
734 exported by the Redis server it is connected to, but were not available
1035 | Command "r" flag removed from commands not accessing the key space.
1399 where not just single bit operations are performed, but the array of
1400 bits composing a string, can be addressed at random, not aligned
1410 some reason looked a bit far fetched or not well specified.
1578 NODES, that is not a stable API and may change frequently depending on
1725 Redis 3.0 is mostly a strict subset of 3.2, you should not have any problem
1732   past versions) files, but not the other way around.
1739 provided. Where not specified the implementation and design is done by