Hi,
>> Van: Stefan Sperling [mailto:stsp_at_elego.de]
>> On Fri, Nov 13, 2009 at 06:19:26PM +0100, Stefan Hett wrote:
>>
>>> Hi,
>>>
>>> thanks for the quick reply. The workaround u described is possible and
>>> prevents this issue from happening.
>>> However, I'm just looking for s/o to verify that this is indeed a bug
>>> and/or whether it is already known before I bother the devs with it. :-)
>>>
>> It works file here without an intermediate commit.
>> I've tested both with trunk and 1.6.x, same result, see below.
>>
>
> Yes, I've also tested this in the past, and it works.
>
> However, there is a special case in which your test provokes a bug: renaming a file back to its original name makes subversion think that you're doing a replace (effectively breaking the line of history). This issue is already known:
>
> http://subversion.tigris.org/issues/show_bug.cgi?id=3429 - "svn mv A B; svn mv B A" generates "replace"
>
> But moving from A to B, and then from B to C, then committing should be no problem.
Thanks. That's exactly how I tested it. It didn't occur to me that it
could be a special case which only occurs when renaming the file back to
the original filename.
Regards,
Stefan
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2417807
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-11-14 02:20:44 CET