svn info command report inconsistent Last Changed Rev for merges/copies

[Joakim Plate <Jo...@qrtech.se>]

Hi

We recently run into an issue with how pegging of externals using TortoiseSVN. TortoiseSVN would peg the revision during a branch/tag operation to a revision where the external did not exist. I've tracked down the issue back to the "svn info" command (subversion 1.8.13).

When svn merges/copies a directory, a file inside that directory will not get an updated "Last Changed Rev" as seen by svn info. While a direct copy/merge of a single file will get the merge/copy revision, even if it results in a direct copy.

Attached example script shows the issue in effect.

>From subversions perspective, either behavior could be considered correct, but it ought to be consistent I think.

I did notice this: http://thread.gmane.org/gmane.comp.version-control.subversion.devel/136663/focus=136719

But seems TortoiseSVN decided to implement behavior based on these "shady definitions" on (LCR, URL). Any changes in stances on this?, alternative some good suggestion for what TortoiseSVN should do instead? Seems svn log gives the correct pegging revision.

/Joakim

Ps. Maybe I should have crossposted to tortoisesvn mailing list here, but wasn't sure it was allowed.


Joakim Plate

QRtech AB
E-mail : joakim.plate@qrtech.se
Web    : www.qrtech.se