Comment #1 on issue 3490 by mgul...@gmail.com: rbt post with Perforce fails when a file has been renamed twice
https://code.google.com/p/reviewboard/issues/detail?id=3490

I have run across this issue as well. I believe the issue is that the 'move/delete' record doesn't have the 'moved into' field. You need to use the file log of the previous revision to find the 'moved into' field.

i.e.
p4 filelog //depot/path/to/originalfile.txt#2
//depot/path/to/originalfile.txt
... #2 change 1235 move/delete on 2014/11/04 by user@client (text) 'rename file'
... #1 change 1234 add on 2014/10/30 by user@client (text) 'create file'
... ... moved into //depot/path/to/renamedfile.txt#1

Note that the 'moved into' record is associated with the previous revision of the file, because that is the revision that was moved (if you were to 'p4 print //depot/path/to/originalfile.txt#2' you would get an empty file)

--
You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.

Reply via email to