Why does monotone read all revisions and certs in the database on a sync?
At least 90% of the time, a comparison between the heads of branches
to sync(A) vs the heads of branches to sync against(B) will result in
either A is before B or B is before A and occasionally neither A or B
is known to
On 06/03/2010 04:21 PM, J Decker wrote:
Why does monotone read all revisions and certs in the database on a sync?
One fairly basic feature monotone has is that certs can be added to
arbitrarily old revisions. What this means for netsync is that just
synchronizing the revision graph isn't
On Thu, Jun 3, 2010 at 2:56 PM, Timothy Brownawell tbrow...@prjek.net wrote:
On 06/03/2010 04:21 PM, J Decker wrote:
Why does monotone read all revisions and certs in the database on a sync?
One fairly basic feature monotone has is that certs can be added to
arbitrarily old revisions. What
On 06/03/2010 06:09 PM, J Decker wrote:
What would probably work is to store a skip-list over the revision graph,
and synchronize on first the leaves (well, probably near-leaves, say
anything not covered by a higher skip-node) at each level and then either
prune/iterate or just synchronize on
