[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: VCP for Foo <-> subversion conversion?

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2002-07-29 18:03:08 CEST

Barrie Slaymaker <barries@slaysys.com> writes:
> Right now, it does change set aggregation (even when copying to cvs,
> though cvs loses this info), though it does not handle
> branching. I'm working on branching and establishing a branch map as we
> speak.

We're interested, yes. To some extent, this duplicates work we've
already been doing on a "cvs2svn" converter, but that's okay. The
only question is, as always, "What's the shortest path from where we
are now to where we want to be?" :-).

Our converter doesn't yet handle branches in the CVS repository
either; and that's also the Next Big Thing on our plate. Sound

> All access is currently through command line invocations for the sake of
> generality and portability (no need to distribute binaries to folks not
> compiler-enabled), but we are planning on building high speed
> direct-to-backend modules.

For big repositories, direct-to-backend is going to be a real win.
We're doing it that way too.

> FWIW, VCP so far has been funded by Perforce thus far and Perforce is
> quite interested in seeing VCP and RevML used as a standard tool for
> interchange between repositories.

Wow. I'm tempted to ask how you handle discrepencies between
repository schemas, but then again, you did point us to a theory link.

When I say we've been working on cvs2svn, I use the term "we" loosely.
In fact, it's been a specific group of people, not including me. So I
think the next step is to see if any of them have taken a look at VCP,
and what their thoughts are. Guys?


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 29 18:17:55 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.