You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Max Bowsher <ma...@ukf.net> on 2003/08/20 14:17:09 UTC
Is it valid for two consecutive subversion revisions to have the same svn:date?
Issue #1362 "cvs2svn resyncing spuriously" has an easy resolution if it is
valid for 2 consecutive subversion revisions to have identical svn:date
properties. Is this valid?
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Is it valid for two consecutive subversion revisions to have the same svn:date?
Posted by Max Bowsher <ma...@ukf.net>.
cmpilato@collab.net wrote:
> "Max Bowsher" <ma...@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
Re: Is it valid for two consecutive subversion revisions to have the same svn:date?
Posted by cm...@collab.net.
"Max Bowsher" <ma...@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.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Is it valid for two consecutive subversion revisions to have the same svn:date?
Posted by Max Bowsher <ma...@ukf.net>.
cmpilato@collab.net wrote:
> "Max Bowsher" <ma...@ukf.net> writes:
>
>> Issue #1362 "cvs2svn resyncing spuriously" has an easy resolution if
>> it is valid for 2 consecutive subversion revisions to have identical
>> svn:date properties. Is this valid?
>
> I've not actually seen a case where I thought cvs2svn's resyncs were
> spurious. Has anyone else, or was the issue based on someone's
> reaction to some presumedly unlikely number of RESYNC print-outs?
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.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Is it valid for two consecutive subversion revisions to have the same svn:date?
Posted by cm...@collab.net.
"Max Bowsher" <ma...@ukf.net> writes:
> Issue #1362 "cvs2svn resyncing spuriously" has an easy resolution if
> it is valid for 2 consecutive subversion revisions to have identical
> svn:date properties. Is this valid?
I've not actually seen a case where I thought cvs2svn's resyncs were
spurious. Has anyone else, or was the issue based on someone's
reaction to some presumedly unlikely number of RESYNC print-outs?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org