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

Re: cvs2svn urgently needs a verification tool

From: <kfogel_at_collab.net>
Date: 2004-02-15 23:02:51 CET

Tobias Ringström <tobias@ringstrom.mine.nu> writes:
> I'm happy to say that it's wasn't nearly as bad as I thought, but it
> is a little strange, and I hope you can help me to shed some light on
> it. I don't have a repos to post right now, but the problem is easy to
> describe at least. (At least how it behaves, not why it happens.)
>
> The CVS repository has a branch label by the name RELEASE_C2_1 set on
> almost all files, but on two files, it was a tag. This caused cvs2svn
> to create both a branch and a tag by the name RELEASE_C2_1. The
> strange thing is that the contents of the branch and the tag differ
> for one single file (which used RELEASE_C2_1 as a branch label).
>
> Any ideas?

Hmm. Are the files on which the symbolic name 'RELEASE_C2_1' exists
*both* as a tag and as a branch label?

I might be missing something here, but... I don't see why the contents
of the branch and the tag *wouldn't* differ on some files. It seems a
perfectly natural outcome. There's no guarantee that when
'RELEASE_C2_1' is a tag, it is associated with the head revisions of
branches of that name.

I guess I'll need to see the actual RCS files.

-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Feb 16 00:05:18 2004

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.