Kelly F. Hickel writes: > > Since 1.11 exhibits the same behavior, and doesn't seem to have a > problem with local repo's (see thread on info-cvs, I think 1.12.13 is > broken in this regard), I'm quantifying 1.11.21 instead....
Now that I understand your problem, I suspect I could have saved you the trouble. The problem is almost certainly RCS_magicrev(), which is the function that finds the new branch number to be used. The way it currently works is to just try all even numbers starting with 2 until it finds one that isn't used as a physical branch and doesn't appear in a magic branch tag. Determining whether a physical branch occurs requires looking through the entire list of existing revisions, and determining whether a magic branch tag exists requires looking through the entire list of tags. As the number of branches increases, the time required for this operation increases quadratically. A reasonable solution would be to rewrite the function to run through each list once, remembering the highest existing branch and then incrementing to the next even number. -Larry Jones When I want an editorial, I'll ASK for it! -- Calvin _______________________________________________ Bug-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/bug-cvs
