summaryrefslogtreecommitdiff
path: root/t/t9601/cvsroot/module
diff options
context:
space:
mode:
authorLibravatar Matheus Tavares <matheus.bernardino@usp.br>2020-12-01 20:45:04 -0300
committerLibravatar Junio C Hamano <gitster@pobox.com>2020-12-02 14:35:51 -0800
commiteb3c027e1779d0d1b5bd3b4e96a108461c9759a5 (patch)
tree31443e01cff697ad2ff0ec3e39f353bd3b4a7e9c /t/t9601/cvsroot/module
parentGit 2.29.2 (diff)
downloadtgif-eb3c027e1779d0d1b5bd3b4e96a108461c9759a5.tar.xz
apply: don't use core.sharedRepository to create working tree files
core.sharedRepository defines which permissions Git should set when creating files in $GIT_DIR, so that the repository may be shared with other users. But (in its current form) the setting shouldn't affect how files are created in the working tree. This is not respected by apply and am (which uses apply), when creating leading directories: $ cat d.patch diff --git a/d/f b/d/f new file mode 100644 index 0000000..e69de29 Apply without the setting: $ umask 0077 $ git apply d.patch $ ls -ld d drwx------ Apply with the setting: $ umask 0077 $ git -c core.sharedRepository=0770 apply d.patch $ ls -ld d drwxrws--- Only the leading directories are affected. That's because they are created with safe_create_leading_directories(), which calls adjust_shared_perm() to set the directories' permissions based on core.sharedRepository. To fix that, let's introduce a variant of this function that ignores the setting, and use it in apply. Also add a regression test and a note in the function documentation about the use of each variant according to the destination (working tree or git dir). Signed-off-by: Matheus Tavares <matheus.bernardino@usp.br> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t9601/cvsroot/module')
0 files changed, 0 insertions, 0 deletions