| commit | b6ad6dcc3b0629d525abc9fe0882e1b0eb969e17 | |
| author | Pete Wyckoff <pw@padd.com> | |
| Mon, 30 Apr 2012 00:57:16 +0000 (29 20:57 -0400) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Mon, 30 Apr 2012 23:00:04 +0000 (30 16:00 -0700) | ||
| tree | 9f00b39820b05293dd65097c8aaf5823c77654ea | treesnapshot (tar.gz zip) |
| parent | 0f224e5b73a73f37887eb7cb3e51073f889a3f9c | commitdiff |
git p4: fix writable file after rename or copy
The way rename works is with a "p4 integrate", optionally
followed by a "p4 edit" if the change is not a 100% rename.
Contents are generated by applying a patch, not doing a file
system rename. Copy is similar.
In this case, p4 does not fix the permissions back to read-only.
Make sure this happens by calling "p4 sync -f".
Signed-off-by: Pete Wyckoff <pw@padd.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
The way rename works is with a "p4 integrate", optionally
followed by a "p4 edit" if the change is not a 100% rename.
Contents are generated by applying a patch, not doing a file
system rename. Copy is similar.
In this case, p4 does not fix the permissions back to read-only.
Make sure this happens by calling "p4 sync -f".
Signed-off-by: Pete Wyckoff <pw@padd.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| git-p4.py | diffblobblamehistory | |
| t/t9807-git-p4-submit.sh | diffblobblamehistory | |
| t/t9809-git-p4-client-view.sh | diffblobblamehistory |