| commit | 7a63c9e3da357a21115e9b5de7ed84b744f9d8b1 | |
| author | Junio C Hamano <gitster@pobox.com> | |
| Wed, 20 Jan 2016 19:43:35 +0000 (20 11:43 -0800) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Wed, 20 Jan 2016 19:43:35 +0000 (20 11:43 -0800) | ||
| tree | 97d1f8f28303c0e0f96e2ae3133f252482d28399 | treesnapshot (tar.gz zip) |
| parent | 85705cfb572878296f26a7fef0d174b5ec694161 | commitdiff |
| parent | ea56518dfe4c7934a6895f25edf0f18d2930e4fd | commitdiff |
Merge branch 'js/fopen-harder'
Some codepaths used fopen(3) when opening a fixed path in $GIT_DIR
(e.g. COMMIT_EDITMSG) that is meant to be left after the command is
done. This however did not work well if the repository is set to
be shared with core.sharedRepository and the umask of the previous
user is tighter. They have been made to work better by calling
unlink(2) and retrying after fopen(3) fails with EPERM.
* js/fopen-harder:
Handle more file writes correctly in shared repos
commit: allow editing the commit message even in shared repos
Some codepaths used fopen(3) when opening a fixed path in $GIT_DIR
(e.g. COMMIT_EDITMSG) that is meant to be left after the command is
done. This however did not work well if the repository is set to
be shared with core.sharedRepository and the umask of the previous
user is tighter. They have been made to work better by calling
unlink(2) and retrying after fopen(3) fails with EPERM.
* js/fopen-harder:
Handle more file writes correctly in shared repos
commit: allow editing the commit message even in shared repos