David, >From my experience, this is the standard behaviour. There is an option to >control this behaviour, though. In your Subversion config file, in the >[miscellany] section, set the use-commit-times option to yes. SVNKit respects >the default Subversion config file.
Alternatively, you could provide an ISVNOptions to SVNKit, where you can specify your desired behaviour. Regards, Biörn ________________________________________ From: svnkit-users-boun...@svnkit.com [svnkit-users-boun...@svnkit.com] on behalf of David Grant [davidgr...@gmail.com] Sent: 03 August 2012 1:12 To: svnkit-users@svnkit.com Subject: Re: Timestamps not updated to current date/time after update I've verified this with SmartSVN as well as the jsvn command-line front-end to SVNkit. I've confirmed that Collabnet svn.exe for Windows does not behave this way (it updates the timestamp to now() on each update regardless), nor does svn in Linux. David Grant wrote: > > After doing an update to an older revision, or back to HEAD, the changed > files' timestamps are not updated to the current date/time. This wrecks > havoc with build systems which rely on timestamps to figure out which > files need rebuilding (ie. which source files are newer than targets). > > Is this expected behaviour? I don't think it is because the svn command > line client doesn't do this. > -- View this message in context: http://old.nabble.com/Timestamps-not-updated-to-current-date-time-after-update-tp34247014p34248553.html Sent from the SVNKit - Users mailing list archive at Nabble.com.
