|
The people have spoken: m7 should use custom certs, not tags. Announcing m7 version 0.2! You can download it at the m7 homepage: http://www.midwinter.com/~lch/programming/m7/ And I'm hoping that someone actually will download it, someday. Maybe even someday soon. This change worked out pretty clean. The custom cert is named m7-db-$username-$computername, whose value is just the revision number. This means you could theoretically populate other people's checkins with local revision numbers and not worry too overly much about collisions. (Though I think that wouldn't be cricket.) However, it's not all skittles and beer. Producing the list of tags with their local revision numbers is a lot slower this way, so now there's a noticable slowdown before the output of tannotate. The price of progress, I guess. Justin Patrin said: Sure, but it's the per-monotone-process overhead that I was really speaking to. I imagine that monotone gets going, it's mighty quick at culling certs from the database. If I could do it all in one invocation of monotone, it would be a hell of a lot quicker than the N invocations I sometimes must use now.Oh, and as for O(1) vs. O(n) I think that's a very false assumption. True, you're going to start more processes, but monotone itself has to do internal things [...] larry |
_______________________________________________ Monotone-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/monotone-devel
