[
https://issues.apache.org/jira/browse/SVN-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Zhakov updated SVN-4334:
-----------------------------
Fix Version/s: (was: 1.8-consider)
1.8.0
> move-update not setting last_mod_time in destination
> ----------------------------------------------------
>
> Key: SVN-4334
> URL: https://issues.apache.org/jira/browse/SVN-4334
> Project: Subversion
> Issue Type: Bug
> Components: libsvn_wc
> Affects Versions: trunk
> Reporter: Philip Martin
> Fix For: 1.8.0
>
>
> {noformat:nopanel=true}
> svnadmin create repo
> svn import -mm repo/format file://`pwd`/repo/A/f
> svnmucc -mm put repo/README.txt file://`pwd`/repo/A/f
> svn co file://`pwd`/repo wc
> svn mv wc/A wc/A2
> A/f and A2/f both have last_mod_time set, that's OK. (Perhaps we should remove
> last_mod_time from the deleted A/f but that's not the bug here.)
> svn up --accept postpone -r1 wc
> A/f has lost_mod_time cleared, thats OK. A2/f unchanged and still has
> last_mod_time.
> svn resolve --accept mc wc/A
> A2/f has last_mod_time cleared, that's a bug. It means the client will have
> to
> do a full-text comparison to detect differences.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
