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

On Wed, Jul 4, 2012 at 2:26 PM, Johan Corveleyn <jcorvel_at_gmail.com> wrote:
> On Wed, Jul 4, 2012 at 2:11 PM, Vincent Lefevre <vincent-svn_at_vinc17.net> wrote:
>> On 2012-07-04 13:58:50 +0200, Johan Corveleyn wrote:
>>> > The problem now is that the URL + the LastChangedRev together can
>>> > no longer identify the file, because the LastChangedRev can now be
>>> > incorrect as a peg revision.
>>>
>>> I'm afraid I don't follow you here either. Can you give a concrete example?
>>
>> Well, this is more complex that I thought, and 1.7 really has an
>> inconsistency. My example is in my reply to Philip Martin.
>
> Ah yes, you're right.
>
> We now have two clearly separate discussions:
>
> - Inconsistencies in LCR between originating WC and repository. That's
> my main interest right now. I think those are clearly bugs (1.6 had
> one, and now 1.7 has another one it seems).

I filed an issue for this:

http://subversion.tigris.org/issues/show_bug.cgi?id=4203 (Commit of
moved dir with modified file in dir/subdir doesn't bump LastChangedRev
of subdir in originating WC)

-- 
Johan