cmpilato@collab.net wrote:
> "Max Bowsher" <maxb@ukf.net> writes:
>
>> Issue URL: http://subversion.tigris.org/issues/show_bug.cgi?id=1362
>> Reported by kfogel.
>>
>> The problem is that when "cvs import" creates a new file, r1.1 and
r1.1.1.1
>> very often have the same time (created within the same second). cvs2svn
>> resyncs 1.1 to seperate these revisions. The result is lots of resyncs,
even
>> though there is nothing "odd" with the cvs respository. If there are no
>> adverse consequences, cvs2svn could resync only when a later revision is
>> strictly earlier, rather than earlier or equal to the preceding revision.
>
> IIRC, if you don't resync to ensure that 1.1.1.1 happens *after* 1.1,
> though, you can't perform the necessary 'svn copy' operation to make
> the branch as a copy of the trunk. Maybe this isn't such a big deal
> -- I don't know enough about RCS or cvs2svn to say.
Oops! You are right - without the resync, cvs2svn can't ensure proper
ordering of the commits.
I will make a note of this in the issue.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Aug 20 18:23:21 2003