[
https://issues.apache.org/jira/browse/SVN-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Foad updated SVN-752:
----------------------------
Component/s: (was: src)
> rev_hunt is broken when revisions are not date-ordered
> ------------------------------------------------------
>
> Key: SVN-752
> URL: https://issues.apache.org/jira/browse/SVN-752
> Project: Subversion
> Issue Type: Bug
> Affects Versions: all
> Reporter: Greg Stein
> Priority: Major
> Fix For: unscheduled
>
>
> {noformat:nopanel=true}
> Currently, rev_hunt performs a binary search over the FS revisions to
> find the revision for a specific time. Howver, it is possible that the
> FS revisions are not in time-order. This could happen for a couple
> different reasons:
> 1) the commit timestamp was altered (e.g. cvs2svn)
> 2) clock skew or clock changes on the server
> We could alter the server to require the timestamps to be
> monotonically increasing, possibly restrict changing of timestamps,
> warn about the problem, and/or simply allow out-of-order dates.
> Note: if we have out-of-order dates, then it probably means that we
> add a new table to the FS to map dates to revisions (without it,
> rev_hunt would need a linear search).
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
