[Monotone-devel] Update not idempotent?

[Nathaniel Smith]

Using my local database, which was sync'ed with off.net in the recent
past, at least, I get the following:

$ monotone --db=monotone.db --branch=net.venge.monotone co ef23 testdir
monotone: expanded selector 'ef23' -> 'i:ef23'
monotone: expanding selection 'ef23'
monotone: expanded to 'ef234249ab230e44cf2155f6bea5b9dbfab710d5'
$ cd testdir
testdir$ monotone update
monotone: warning: update edge ef234249ab230e44cf2155f6bea5b9dbfab710d5 -> 
af7d791d87b8b348f20715172fea16606b640b16 ignored since it exits branch 
net.venge.monotone
monotone: selected update target 27f0f2c9a47c1f0414cec1c11e8d9523dc8f52bd
monotone: calculating patchset for update
[many "updating file" messages elided]
monotone: updated to base version 27f0f2c9a47c1f0414cec1c11e8d9523dc8f52bd
testdir$ monotone update
monotone: selected update target 8c7a148cb4f57c289cc2c0bdea200d69595c613a
monotone: calculating patchset for update
monotone: updating file ChangeLog: 2a3a53e86ace6e968727645b537a2ff98dd2bb5a -> 
d95b5dc25c03d9eba9bbed864004222aa2514c9d
monotone: updated to base version 8c7a148cb4f57c289cc2c0bdea200d69595c613a
testdir$ 

I find this puzzling, to say the least.  Surely if 8c7a is a good
target the second time, it's a good target the first time?

-- Nathaniel

-- 
Damn the Solar System.  Bad light; planets too distant; pestered with
comets; feeble contrivance; could make a better one myself.
  -- Lord Jeffrey