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

Re: Providing new version of repository for a check-in

From: allan juul <allan_at_muly.dk>
Date: 2005-08-08 20:20:28 CEST

Aaron Wood wrote:

> All,
> I'm working on setting my group up for transitioning to svn from
> cvsnt. To give us a sane, usable history in svn, my plan was to take
> the last n "daily" builds that we tagged in cvs, and dump each of
> those into svn. However, it seems like in order to do this, I'll need
> to:
> 1) export tag from cvs
> 2) checkout latest trunk from svn, into a different folder
> 3) write a script to recursively copy over the export from cvs,
> removing all non-subversion files from the svn WC that aren't in the
> cvs export, and adding all files that are in the cvs export but not in
> the svn WC, as well as copying over all files that exist in both
> locations.
> This seems like something that svn should be able to do somewhat on
> it's own (take a directory structure and just consider that the "new
> revision" of the respository.
> Am I out of luck, or just missing something? svndump is out of the
> question, as I need to have this automated on a build server that's
> talking remotely to the cvs/svn server.
> Thanks much,
> Aaron

what's wrong with cvs2svn ?



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 8 20:22:03 2005

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

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