On Thu, Jan 26, 2006 at 03:58:31AM -0800, Nathaniel Smith wrote: > The current plan for handling double-root trees is just to add the > root renaming feature to mainline. There is a branch for this -- > net.venge.monotone.root-dir-rename. The basic functionality is > implemented, but untested -- in theory you should be able to use this > branch to rosterify a double-root tree, but I have not even tried > compiling it yet, so no guarantees :-). (And also, no guarantees that > the resulting db will be supported going forward -- just use this for > testing for now.) I gave this a whirl on a OE db snapshot, which has multiple roots. It seems to have done something sensible (diff -r of a 0.25 and rdr co returns only MT/ differences)
More importantly, a fresh pull is almost 7 times faster with rosters. Good work! --Jack --- $ /bin/time monotone-0.25 --db=0.25-test-pull.db pull 127.0.0.1 \* monotone: setting default server to 127.0.0.1 monotone: setting default branch include pattern to '*' monotone: setting default branch exclude pattern to '' monotone: connecting to 127.0.0.1 monotone: first time connecting to server 127.0.0.1 monotone: I'll assume it's really them, but you might want to double-check monotone: their key's fingerprint: 6d8885f8879bf9c1fa383a9c93e54aa299c52232 monotone: finding items to synchronize: monotone: bytes in | bytes out | certs in | revs in | revs written monotone: 36.9 M | 1.7 M | 16378 | 4201 | 1 monotone: verifying new revisions (this may take a while) monotone: bytes in | bytes out | certs in | revs in | revs written monotone: 38.2 M | 1.7 M | 16378 | 4201 | 4201 monotone: successful exchange with 127.0.0.1 28718.62user 353.52system 8:10:54elapsed 98%CPU (0avgtext+0avgdata 0maxresident)k 0inputs+0outputs (917major+92769803minor)pagefaults 0swaps --- $ /bin/time monotone-rdr --db=rdr-test-pull.db pull 127.0.0.1 \* monotone: setting default server to 127.0.0.1 monotone: setting default branch include pattern to '*' monotone: setting default branch exclude pattern to '' monotone: connecting to 127.0.0.1 monotone: first time connecting to server 127.0.0.1 monotone: I'll assume it's really them, but you might want to double-check monotone: their key's fingerprint: 6d8885f8879bf9c1fa383a9c93e54aa299c52232 monotone: finding items to synchronize: monotone: bytes in | bytes out | certs in | revs in monotone: 36.5 k | 785 | 0 | 0 monotone: bytes in | bytes out | certs in | revs in monotone: 36.3 M | 833 | 16264/16264 | 4201/4201 monotone: successful exchange with 127.0.0.1 4274.98user 92.84system 1:18:08elapsed 93%CPU (0avgtext+0avgdata 0maxresident)k 0inputs+0outputs (900major+16710262minor)pagefaults 0swaps --- -- Jack (John) Cummings http://mudshark.org/ PGP fingerprint: 0774 D073 E386 B70B 6B16 2D2B 1DD8 F8B0 CCF0 FAEE Now playing on Prime: Breaking the Girl -- Red Hot Chili Peppers Now playing on Remedial: Kite -- U2
pgp0UfS05jCfu.pgp
Description: PGP signature
_______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel