issue#752: date-based revision selection can fail

Hi,

I've just been bitten by bug#752 and wanted to remind SVN developers
about it; real people (me at least!) are being hit by this.

I spent a day or so wondering why official binaries of release 1.0.4 of
apache commons logging (released 2004-06-12) throw an exception in a new
test, while code compiled from "svn co -r {2004-06-12} ..." works fine.
I presumed the issue was something to do with the build environment, but
eventually discovered that the result of the checkout actually included
patches added many months after the specified date :-(.

I believe the reason is exactly as described in #752: CVS imports have
been done via cvs2svn which mean new commits applied with "backdated"
timestamps or somesuch, thereby stuffing up subversion's date-based
indexes.

I'll just be extra-careful to use revision numbers only in future, but
it would be lovely if someone could find time to address this.

By the way: thanks for subversion - it's a very very cool tool.

Regards,

Simon

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun May 22 09:57:20 2005