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

Re: Possible bug in cvs2svn.py

From: <kfogel_at_collab.net>
Date: 2004-02-20 17:06:42 CET

Jeff Squyres <jsquyres@lam-mpi.org> writes:
> So I went and got the most recent subversion (r8786), and ran that
> cvs2svn.py on my large CVS repository. The large commit time problem went
> away.
> But here's a new wrinkle -- it created a bunch of small directories named
> "unlabeled-x.y.z" in the branches/ subdirectory in the new SVN repository.
> I had a look at some of the files in there, and they're typically very
> small sets of files (i.e., it looks like one changeset), but there's no
> obvious branch tag in the original CVS repository for that commit.
> What are these unlabeled branches?

Ah, thank you for asking -- now I know something I need to document.

Those are for branches that don't have labels (symbolic names). This
is quite possible in an RCS file. Look in the revision header section
of some of those RCS files, you'll see branch commits, yet the
symbolic names section will have no label for that branch.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 20 18:09:41 2004

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.