finishing cvs2svn

As you might have guessed from my recent SWIG build woes... :-)

I'm trying to gather the disparate strands of cvs2svn development and
finish the thing already. Even though it's not a 1.0 necessity from
Subversion's point of view, it's still something we'll need for
Subversion to see widespread adoption.

Here's what I know about right now:

  1. Marko Macek has a branch, cvs2svn-mmacek/, which contains some
     improvements he made to cvs2svn. These need to be reviewed and
     possibly incorporated. Among other things, there is code for
     handling branches and tags.

  2. We have some issues filed, now grouped together in the
     "cvs2svn-*" milestones:

        1106 cvs2svn-1.0 cvs2svn: control chars in CVS logs not handled
         983 cvs2svn-1.0 cvs2svn.py: Non-ASCII characters garbled
        1105 cvs2svn-1.0 cvs2svn doesn't respect executable bit
        1115 cvs2svn-opt cvs2svn.py should discover moves/copies

     (Issue #1105 is also addressed on Marko's branch.)

  3. Two patches that were posted to this list:

        Marko Macek:
          "cvs2svn optimized tag/branch conversion (work in progress)"

        Michael Wood:
          "cvs2svn/README" (just a quick doc tweak)

     (Maybe Marko's posted patch is already incorporated in his
     branch? Don't know yet, but that'll be easy to figure out.)

So, anyone know of anything else out there? Speak now or forever hold
your peace :-).

-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Feb 21 21:17:06 2003