Comment #1 on issue 3490 by mgul...@gmail.com: rbt post with Perforce fails
when a file has been renamed twice
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.
p4 filelog //depot/path/to/originalfile.txt#2
... #2 change 1235 move/delete on 2014/11/04 by user@client (text) 'rename
... #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
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
To post to this group, send email to firstname.lastname@example.org.
Visit this group at http://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.