Re: svn copy not updating Last Changed Rev

On Mon, Mar 29, 2010 at 14:02:06 -0400, Bob Archer wrote:
> Why would you expect the last changed rev of a file to change just
> because you coppied it to another path? You didn't actually change
> that file right?

First, the value changes if you use svn copy locally and commit the
results. So I would expect the behavior of using svn copy using two URLs
to have the same behavior.

Second, the revision shows up in the log for that file. So there is an
inconsistency here. Either the file was changed and the log is correct,
or nothing changed and the log shouldn't really be there either.

Finally, you could just as easily argue that branches/mine/ is a copy of
trunk/ and did not actually change either. So why would that have an
updated revision number but nothing else does?

I should add that I only showed this on a file, but it actually happens
to both files and directories beneath the root of the copy operation.

-- 
Jon
"lib64 is a wart on history and should never have been there."
        -Tollef Fog Heen