Re: cvs2svn.py

> > We could have cvs2svn act the same as 'cvs log' and just drop the second
> > symbol.
> > Maybe as an option? strict vs lenient mode?
>
> Yes, that wood be a good solution.
>
> I did not change the repository in any way by hand. It has all been
> generated by CVS itself. This "MFuchs" and "v1" have been generated as
> vendor-tag and release-tag from the "cvs import" command. They can be found
> on any file in the same directory. I don't know what happened exacty when
> importing the files, may be there has occured some error. I even do not
> know, what this "vendor" and "release" tags are needed for. I would not use
> them, if "cvs import" would not explicitely demand them.

Now i could find, what may have caused the problem. If I import a module twice in cvs, I get this duplicate 1.1.1 tags:

y>cvs import test1 vendor1 release1
N test1/1.txt

No conflicts created by this import

>cvs import test1 vendor2 release2
U test1/1.txt

No conflicts created by this import

Martin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Sep 2 23:48:05 2003