monotone-commits-nodiffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Monotone-commits-nodiffs] Revision 64c11610f5e6dc2a8ad7b98dc187147d6aea


From: monotone
Subject: [Monotone-commits-nodiffs] Revision 64c11610f5e6dc2a8ad7b98dc187147d6aeabae1
Date: Tue, 6 Nov 2007 20:07:46 +0100

-----------------------------------------------------------------
Revision: 64c11610f5e6dc2a8ad7b98dc187147d6aeabae1
Ancestor: 059e2edb2dcae9febd6e4cbcb609cde6ae0e4230
Author: address@hidden
Date: 2007-10-19T07:27:21
Branch: net.venge.monotone.cvsimport-branch-reconstruction

Modified files:
        rcs_import.cc

ChangeLog: 

* Optimize away lots of sort steps: the blob's events need to be ordered
  by increasing timestamp for all of the blob splitting and branch
  sanitizing steps. Only after that, as soon as a blob is being
  consumed, we need another ordering for the cvs revision info attribute:
  the events need to be ordered by pathname there.
  Anyway, we remember per blob, if we've already sorted the events or
  not. Splitting a blob does not reset that flag, as it does not change
  the ordering of the events.


monotone --db={your.database} diff 
--revision=059e2edb2dcae9febd6e4cbcb609cde6ae0e4230 
--revision=64c11610f5e6dc2a8ad7b98dc187147d6aeabae1
----------------------------------------------------------------------




reply via email to

[Prev in Thread] Current Thread [Next in Thread]