So the problem is with conversion from CVS to SVN? Does this problem creep up on repositories that have used SVN from the start? Does it happen when you consolidate svn repositories into a single repo?
On Mon, Nov 17, 2008 at 5:19 PM, Larry Shatzer, Jr. <larrys@...> wrote:
One word of caution, it is not just the ASF repository that has this
problem, but possibly others. At my work our repository is in a
similar situation. We converted a few CVS repositories separately, and
consolidated a few Subversion repositories into a single repository.
So now we have the same issue. I am not sure of any other public
Subversion server that might have this issue.