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

Re: Incorrect LastChangedRev in working copy after committing directory move + modified file in subdir

From: Vincent Lefevre <vincent-svn_at_vinc17.net>
Date: Tue, 3 Jul 2012 14:09:12 +0200

On 2012-07-03 13:21:35 +0200, Johan Corveleyn wrote:
> I just tested my scenario with 1.6: it doesn't have the same issue
> (subdir has LastChangedRev 3 in both the working copy and the
> repository). So this is a regression in 1.7.

The reason why "subdir" has LastChangedRev 3 may be because its parent
directory "dir" was renamed to "dir2": with Subversion 1.6, when a
directory was copied, all its descendents had their LastChangedRev
bumped to this commit revision. Do you confirm?

Could you try the same test without modifying test.txt in rev 3?
I think you'll also see LastChangedRev 3 on subdir with 1.6.

Vincent Lefèvre <vincent@vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Received on 2012-07-03 14:09:45 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.