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

cvs2svn + vendor branch woes

From: Michael Sperber [Mr. Preprocessor] <sperber_at_informatik.uni-tuebingen.de>
Date: 2003-05-05 15:51:09 CEST

This must be a well-known issue, but I didn't find anything
illuminating in the mailing list or in Issuezilla, so I'll ask anyway:

I can see why getting cvs2svn to work on branches is hard, and it
isn't absolutely necessary for traction with a lot of real-life

However, one thing that's been supremely annoying is that cvs2svn
doesn't handle the trunk-nature of vendor branches up to the first
change right. This has completely messed up all CVS -> Subversion
conversions I've done so far, even though I didn't have any real
branches in the CVS repos.

I see the commented-out branch support in the current version
cvs2svn.py does refer to the vendor branch. Does that aspect of
branch support work correctly and might it make sense to enable it
selectively, without doing full branches?

Any help would be much appreciated!

Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon May 5 15:51:59 2003

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.