Comment 27 for bug 405317

Sorry for the late reply; I've been on vacation ;-)
I agree with your analysis.
Because the original repository was damaged beyond repair I've created a fully new repository which currently has only around 100 revisions in 4 branches and do not currently see this problem.
I think this is more-or-less a duplicate of the content-filtering bug.