On Tue, Oct 14, 2008 at 10:56 PM, Stephen Leake
<address@hidden> wrote:
'mtn automate get_corresponding_path' takes the name in the current
rev and gives you the name in some parent rev.
... gives you the name in some *specified* parent rev, meaning, take this name, look it up in that rev, and get the node id. At least that's how I understand it.
You can use that before invoking this log, or log could do it
automatically.
I would argue log should do that automatically.
Any given name can map to many different node ids through time. Should log include *all* of them? It might take some time to load every historical roster and check to see if the specified name maps to a known node there.
Cheers,