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

Re: Behavior when revision dates are out-of-order

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-03-14 20:05:57 CET

On Mar 14, 2005, at 12:54 PM, Steve Greenland wrote:

> On Sun, Mar 13, 2005 at 12:36:40PM -0800, Eric Hanchrow wrote:
>> I'm pretty sure you can modify the dates on commits yourself. Try
>> "svn propedit --revprop svn:date XXXX" where XXXX is the proper date
>> format.
> I don't think the problem was the dates, but that the (converted)
> commit
> dates are not in sequence with the revision numbers. This actually
> isn't
> wrong[1], per se, but it can be confusing.
> None of which answers Felix's original question...

Subversion's ability to convert a -r{datestring} into a specific
revision number is completely dependent on the repository revisions'
datestamps being in chronological order. It does a binary search on
the datestrings to hone-in on the specific revision. If the revisions'
datestamps are out of order, the binary search might return really
weird results.

This is a known issue, as old as the hills, issue #752.

There's no workaround.

If admins load new dumpfiles onto the end of existing repositories,
this is a currently unavoidable side-effect. You need to tell your
users to stop using -r{DATE}.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Mar 14 20:08:27 2005

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.