lorneli 5096b4ed5d clientv3/ordering: compare and update prevRev atomically ... Several goroutines may call setPrevRev concurrently with different revisions, all higher than prevRev. Previously all of these goroutines could set prevRev, so prevRev may be replaced by older one. If response's revision equals to prevRev, there's no need to call setPrevRev.		2017-10-09 20:06:19 +08:00
..
doc.go	ordering: use x/net/context and add doc.go	2017-07-26 20:58:41 -07:00
kv.go	clientv3/ordering: compare and update prevRev atomically	2017-10-09 20:06:19 +08:00
kv_test.go	clientv3/ordering: add missing 'errOrderViolation' error check	2017-10-03 18:04:36 -07:00
util.go	clientv3: goword spelling check	2017-09-06 22:11:33 -07:00
util_test.go	*: fix 'ineffassign' issues	2017-10-03 10:14:33 -07:00