{"thread":{"id":"10301","subject":"[PATCH] git-p4 support for perforce renames.","startedAt":"2007-10-16T04:35:45Z","lastAt":"2007-10-16T04:35:45Z","messageCount":1,"participants":["Chris Pettitt"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"55943","messageId":"1192509345-21340-1-git-send-email-cpettitt@gmail.com","threadId":"10301","inReplyTo":null,"subject":"[PATCH] git-p4 support for perforce renames.","fromName":"Chris Pettitt","fromEmail":"cpettitt@gmail.com","sentAt":"2007-10-16T04:35:45Z","receivedAt":"2007-10-16T04:35:45Z","isPatch":true,"sender":{"key":"cpettitt@gmail.com","avatar":null},"body":"The current git-p4 implementation does support file renames. However, because\nit does not use the \"p4 integrate\" command, the history for the renamed file is\nnot linked to the new file.\n\nThis changeset adds support for perforce renames with the integrate command.\nCurrently this feature is only enabled when calling git-p4 submit with the -M\noption. This is intended to look and behave similar to the \"detect renames\"\nfeature of other git commands.\n\nThe following sequence is used for renamed files:\n\n    p4 integrate -Dt x x'\n    p4 edit x'\n    rm x'\n    git apply\n    p4 delete x\n\nBy default, perforce will not allow an integration with a target file that has\nbeen deleted. That is, if x' in the example above is the name of a previously\ndeleted file then perforce will fail the integrate. The -Dt option tells\nperforce to allow the target of integrate to be a previously deleted file.\n\nSigned-off-by: Chris Pettitt <cpettitt@gmail.com>\n\n contrib/fast-import/git-p4 |   12 +++++++++++-\n 1 files changed, 11 insertions(+), 1 deletions(-)\n-- \n1.5.3.4.206.g58ba4\n"}]}