From: Mark Mentovai <mark@chromium.org>
To: Git Development <git@vger.kernel.org>
Cc: Junio C Hamano <gitster@pobox.com>,
Chandra Pratap <chandrapratap3519@gmail.com>,
Johannes Schindelin <johannes.schindelin@gmx.de>,
Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Subject: [PATCH v2 0/2] apply: set file mode when --reverse creates a deleted file
Date: Fri, 23 May 2025 13:21:52 -0400 [thread overview]
Message-ID: <20250523172154.93810-1-mark@chromium.org> (raw)
In-Reply-To: <20250522220235.8650-1-mark@chromium.org>
Commit 01aff0a (apply: correctly reverse patch's pre- and post-image
mode bits, 2023-12-26) revised reverse_patches() to maintain the desired
property that when only one of patch::old_mode and patch::new_mode is
set, the mode will be carried in old_mode. That property is generally
correct, with one notable exception: when creating a file, only new_mode
will be set. Since reversing a deletion results in a creation, new_mode
must be set in that case.
Omitting handling for this case means that reversing a patch that
removes an executable file will not result in the executable permission
being set on the re-created file.
Changes from v1:
* Reword the commit message as requested.
* Refactor the new test in accordance with review feedback, splitting it
up and increasing coverage.
* Introduce another new test for the specific problem that commit
01aff0a (apply: correctly reverse patch's pre- and post-image mode
bits, 2023-12-26) fixed.
Mark Mentovai (2):
t4129: test that git apply warns for unexpected mode changes
apply: set file mode when --reverse creates a deleted file
apply.c | 2 +-
t/t4129-apply-samemode.sh | 209 +++++++++++++++++++++++++++++++++++++-
2 files changed, 205 insertions(+), 6 deletions(-)
Range-diff against v1:
-: ------------ > 1: a0af8d15f664 t4129: test that git apply warns for unexpected mode changes
1: 457ab75888cc ! 2: 00760c9ec492 apply: set file mode when --reverse creates a deleted file
@@ Commit message
apply: set file mode when --reverse creates a deleted file
Commit 01aff0a (apply: correctly reverse patch's pre- and post-image
- mode bits; 2023-12-26) revised reverse_patches() to maintain the desired
+ mode bits, 2023-12-26) revised reverse_patches() to maintain the desired
property that when only one of patch::old_mode and patch::new_mode is
set, the mode will be carried in old_mode. That property is generally
- correct, with one notable notable exception: when creating a file, only
- new_mode will be set. Since reversing a deletion results in a creation,
- new_mode must be set in that case.
+ correct, with one notable exception: when creating a file, only new_mode
+ will be set. Since reversing a deletion results in a creation, new_mode
+ must be set in that case.
- Omitting handling for this case meant that reversing a patch that
- removed an executable file would not result in the executable permission
- being set on the re-created file.
+ Omitting handling for this case means that reversing a patch that
+ removes an executable file will not result in the executable permission
+ being set on the re-created file. Existing test coverage for file modes
+ focuses only on mode changes of existing files.
- When git apply --reverse is used, reverse_patches() will now additionaly
- swap old_mode and new_mode for what's represented in the patch as a file
- deletion, as it is transformed into a file creation under reversal.
+ Swap old_mode and new_mode in reverse_patches() for what's represented
+ in the patch as a file deletion, as it is transformed into a file
+ creation under reversal. This causes git apply --reverse to set the
+ executable permission properly when re-creating a deleted executable
+ file.
- Tests are added that ensure that git apply sets file modes correctly on
- file creation, both in the normal (forward) and reverse direction.
- Existing test coverage for file modes focused only on mode changes of
- existing files, and only in the forward direction.
+ Add tests ensuring that git apply sets file modes correctly on file
+ creation, both in the forward and reverse directions.
Signed-off-by: Mark Mentovai <mark@chromium.org>
@@ apply.c: static void reverse_patches(struct patch *p)
SWAP(p->lines_added, p->lines_deleted);
## t/t4129-apply-samemode.sh ##
-@@ t/t4129-apply-samemode.sh: test_expect_success 'git apply respects core.fileMode' '
+@@ t/t4129-apply-samemode.sh: test_expect_success POSIXPERM 'do not use core.sharedRepository for working tree
+ )
+ '
+
++test_file_mode_common() {
++ test -n "$1" && test_grep "^10$1 " "$2" || test_must_be_empty "$2"
++}
++
+ test_file_mode_staged () {
+ git ls-files --stage -- "$2" >ls-files-output &&
+- test_grep "^10$1 " ls-files-output
++ test_file_mode_common "$1" ls-files-output
+ }
- git apply patch 2>err &&
- test_grep ! "has type 100644, expected 100755" err &&
-+ git reset --hard &&
+ test_file_mode_HEAD () {
+ git ls-tree HEAD -- "$2" >ls-tree-output &&
+- test_grep "^10$1 " ls-tree-output
++ test_file_mode_common "$1" ls-tree-output
+ }
- git apply --cached patch 2>err &&
-- test_grep ! "has type 100644, expected 100755" err
-+ test_grep ! "has type 100644, expected 100755" err &&
-+ git reset --hard
+ test_expect_success 'git apply respects core.fileMode' '
+@@ t/t4129-apply-samemode.sh: test_expect_success 'git apply warns about incorrect file modes' '
+ test_file_mode_HEAD 0755 mode_test
+ '
+
++test_expect_success 'setup: git apply [--reverse] restores file modes (change_x_to_notx)' '
++ test_config core.fileMode false &&
++
++ touch change_x_to_notx &&
++ git add --chmod=+x change_x_to_notx &&
++ test_file_mode_staged 0755 change_x_to_notx &&
++ test_tick && git commit -m "add change_x_to_notx as executable" &&
++ test_file_mode_HEAD 0755 change_x_to_notx &&
++
++ git add --chmod=-x change_x_to_notx &&
++ test_file_mode_staged 0644 change_x_to_notx &&
++ test_tick && git commit -m "make change_x_to_notx not executable" &&
++ test_file_mode_HEAD 0644 change_x_to_notx &&
++
++ git rm change_x_to_notx &&
++ test_file_mode_staged "" change_x_to_notx &&
++ test_tick && git commit -m "remove change_x_to_notx" &&
++ test_file_mode_HEAD "" change_x_to_notx &&
++
++ git format-patch -o patches -3 &&
++ mv patches/0001-* change_x_to_notx-0001-create-0755.patch &&
++ mv patches/0002-* change_x_to_notx-0002-chmod-0644.patch &&
++ mv patches/0003-* change_x_to_notx-0003-delete.patch &&
++
++ test_grep "^new file mode 100755$" change_x_to_notx-0001-create-0755.patch &&
++ test_grep "^old mode 100755$" change_x_to_notx-0002-chmod-0644.patch &&
++ test_grep "^new mode 100644$" change_x_to_notx-0002-chmod-0644.patch &&
++ test_grep "^deleted file mode 100644$" change_x_to_notx-0003-delete.patch
+'
+
-+test_expect_success 'git apply restores file modes' '
++test_expect_success 'git apply restores file modes (change_x_to_notx)' '
+ test_config core.fileMode false &&
-+ echo "This is data, do not execute!" >data.txt &&
-+ git add --chmod=+x data.txt &&
-+ git ls-files -s data.txt >ls-files-output &&
-+ test_grep "^100755" ls-files-output &&
-+ test_tick && git commit -m "Add data" &&
-+ git ls-tree -r HEAD data.txt >ls-tree-output &&
-+ test_grep "^100755" ls-tree-output &&
-+ git checkout -- data.txt &&
-+
-+ git add --chmod=-x data.txt &&
-+ git ls-files -s data.txt >ls-files-output &&
-+ test_grep "^100644" ls-files-output &&
-+ test_tick && git commit -m "Make data non-executable" &&
-+ git ls-tree -r HEAD data.txt >ls-tree-output &&
-+ test_grep "^100644" ls-tree-output &&
-+ git checkout -- data.txt &&
-+
-+ git rm data.txt &&
-+ git ls-files -s data.txt >ls-files-output &&
-+ test_must_be_empty ls-files-output &&
-+ test_tick && git commit -m "Remove data" &&
-+ git ls-tree -r HEAD data.txt >ls-tree-output &&
-+ test_must_be_empty ls-tree-output &&
-+
-+ git format-patch HEAD~3..HEAD~2 --stdout >patch &&
-+ test_grep "^new file mode 100755$" patch &&
-+ git apply --index patch &&
-+ git ls-files -s data.txt >ls-files-output &&
-+ test_grep "^100755" ls-files-output &&
-+ test_tick && git commit -m "Re-add data" &&
-+ git ls-tree -r HEAD data.txt >ls-tree-output &&
-+ test_grep "^100755" ls-tree-output &&
-+
-+ git format-patch HEAD~3..HEAD~2 --stdout >patch &&
-+ test_grep "^old mode 100755$" patch &&
-+ test_grep "^new mode 100644$" patch &&
-+ git apply --index patch 2>err &&
-+ test_grep ! "has type 100644, expected 100755" err &&
-+ git ls-files -s data.txt >ls-files-output &&
-+ test_grep "^100644" ls-files-output &&
-+ test_tick && git commit -m "Redo data mode change" &&
-+ git ls-tree -r HEAD data.txt >ls-tree-output &&
-+ test_grep "^100644" ls-tree-output &&
-+
-+ git format-patch HEAD~3..HEAD~2 --stdout >patch &&
-+ test_grep "^deleted file mode 100644$" patch &&
-+ git apply --index patch 2>err &&
-+ test_grep ! "has type 100755, expected 100644" err &&
-+ git ls-files -s data.txt >ls-files-output &&
-+ test_must_be_empty ls-files-output &&
-+ test_tick && git commit -m "Redo data removal" &&
-+ git ls-tree -r HEAD tool.sh >ls-tree-output &&
-+ test_must_be_empty ls-tree-output
++
++ git apply --index change_x_to_notx-0001-create-0755.patch &&
++ test_file_mode_staged 0755 change_x_to_notx &&
++ test_tick && git commit -m "redo: add change_x_to_notx as executable" &&
++ test_file_mode_HEAD 0755 change_x_to_notx &&
++
++ git apply --index change_x_to_notx-0002-chmod-0644.patch 2>err &&
++ test_grep ! "has type 100.*, expected 100.*" err &&
++ test_file_mode_staged 0644 change_x_to_notx &&
++ test_tick && git commit -m "redo: make change_x_to_notx not executable" &&
++ test_file_mode_HEAD 0644 change_x_to_notx &&
++
++ git apply --index change_x_to_notx-0003-delete.patch 2>err &&
++ test_grep ! "has type 100.*, expected 100.*" err &&
++ test_file_mode_staged "" change_x_to_notx &&
++ test_tick && git commit -m "redo: remove change_notx_to_x" &&
++ test_file_mode_HEAD "" change_x_to_notx
+'
+
-+test_expect_success 'git apply --reverse restores file modes' '
++test_expect_success 'git apply --reverse restores file modes (change_x_to_notx)' '
+ test_config core.fileMode false &&
-+ echo true >tool.sh &&
-+ git add --chmod=-x tool.sh &&
-+ git ls-files -s tool.sh >ls-files-output &&
-+ test_grep "^100644" ls-files-output &&
-+ test_tick && git commit -m "Add tool" &&
-+ git ls-tree -r HEAD tool.sh >ls-tree-output &&
-+ test_grep "^100644" ls-tree-output &&
-+
-+ git add --chmod=+x tool.sh &&
-+ git ls-files -s tool.sh >ls-files-output &&
-+ test_grep "^100755" ls-files-output &&
-+ test_tick && git commit -m "Make tool executable" &&
-+ git ls-tree -r HEAD tool.sh >ls-tree-output &&
-+ test_grep "^100755" ls-tree-output &&
-+ git checkout -- tool.sh &&
-+
-+ git rm tool.sh &&
-+ git ls-files -s tool.sh >ls-files-output &&
-+ test_must_be_empty ls-files-output &&
-+ test_tick && git commit -m "Remove tool" &&
-+ git ls-tree -r HEAD tool.sh >ls-tree-output &&
-+ test_must_be_empty ls-tree-output &&
-+
-+ git format-patch -1 --stdout >patch &&
-+ test_grep "^deleted file mode 100755$" patch &&
-+ git apply --index --reverse patch &&
-+ git ls-files -s tool.sh >ls-files-output &&
-+ test_grep "^100755" ls-files-output &&
-+ test_tick && git commit -m "Undo tool removal" &&
-+ git ls-tree -r HEAD tool.sh >ls-tree-output &&
-+ test_grep "^100755" ls-tree-output &&
-+
-+ git format-patch HEAD~3..HEAD~2 --stdout >patch &&
-+ test_grep "^old mode 100644$" patch &&
-+ test_grep "^new mode 100755$" patch &&
-+ git apply --index --reverse patch 2>err &&
-+ test_grep ! "has type 100644, expected 100755" err &&
-+ git ls-files -s tool.sh >ls-files-output &&
-+ test_grep "^100644" ls-files-output &&
-+ test_tick && git commit -m "Undo tool mode change" &&
-+ git ls-tree -r HEAD tool.sh >ls-tree-output &&
-+ test_grep "^100644" ls-tree-output &&
-+
-+ git format-patch HEAD~5..HEAD~4 --stdout >patch &&
-+ test_grep "^new file mode 100644$" patch &&
-+ git apply --index --reverse patch 2>err &&
-+ test_grep ! "has type 100755, expected 100644" err &&
-+ git ls-files -s tool.sh >ls-files-output &&
-+ test_must_be_empty ls-files-output &&
-+ test_tick && git commit -m "Undo tool addition" &&
-+ git ls-tree -r HEAD tool.sh >ls-tree-output &&
-+ test_must_be_empty ls-tree-output
- '
-
++
++ git apply --index --reverse change_x_to_notx-0003-delete.patch &&
++ test_file_mode_staged 0644 change_x_to_notx &&
++ test_tick && git commit -m "undo: remove change_x_to_notx" &&
++ test_file_mode_HEAD 0644 change_x_to_notx &&
++
++ git apply --index --reverse change_x_to_notx-0002-chmod-0644.patch 2>err &&
++ test_grep ! "has type 100.*, expected 100.*" err &&
++ test_file_mode_staged 0755 change_x_to_notx &&
++ test_tick && git commit -m "undo: make change_x_to_notx not executable" &&
++ test_file_mode_HEAD 0755 change_x_to_notx &&
++
++ git apply --index --reverse change_x_to_notx-0001-create-0755.patch 2>err &&
++ test_grep ! "has type 100.*, expected 100.*" err &&
++ test_file_mode_staged "" change_x_to_notx &&
++ test_tick && git commit -m "undo: add change_x_to_notx as executable" &&
++ test_file_mode_HEAD "" change_x_to_notx
++'
++
++test_expect_success 'setup: git apply [--reverse] restores file modes (change_notx_to_x)' '
++ test_config core.fileMode false &&
++
++ touch change_notx_to_x &&
++ git add --chmod=-x change_notx_to_x &&
++ test_file_mode_staged 0644 change_notx_to_x &&
++ test_tick && git commit -m "add change_notx_to_x as not executable" &&
++ test_file_mode_HEAD 0644 change_notx_to_x &&
++
++ git add --chmod=+x change_notx_to_x &&
++ test_file_mode_staged 0755 change_notx_to_x &&
++ test_tick && git commit -m "make change_notx_to_x executable" &&
++ test_file_mode_HEAD 0755 change_notx_to_x &&
++
++ git rm change_notx_to_x &&
++ test_file_mode_staged "" change_notx_to_x &&
++ test_tick && git commit -m "remove change_notx_to_x" &&
++ test_file_mode_HEAD "" change_notx_to_x &&
++
++ git format-patch -o patches -3 &&
++ mv patches/0001-* change_notx_to_x-0001-create-0644.patch &&
++ mv patches/0002-* change_notx_to_x-0002-chmod-0755.patch &&
++ mv patches/0003-* change_notx_to_x-0003-delete.patch &&
++
++ test_grep "^new file mode 100644$" change_notx_to_x-0001-create-0644.patch &&
++ test_grep "^old mode 100644$" change_notx_to_x-0002-chmod-0755.patch &&
++ test_grep "^new mode 100755$" change_notx_to_x-0002-chmod-0755.patch &&
++ test_grep "^deleted file mode 100755$" change_notx_to_x-0003-delete.patch
++'
++
++test_expect_success 'git apply restores file modes (change_notx_to_x)' '
++ test_config core.fileMode false &&
++
++ git apply --index change_notx_to_x-0001-create-0644.patch &&
++ test_file_mode_staged 0644 change_notx_to_x &&
++ test_tick && git commit -m "redo: add change_notx_to_x as not executable" &&
++ test_file_mode_HEAD 0644 change_notx_to_x &&
++
++ git apply --index change_notx_to_x-0002-chmod-0755.patch 2>err &&
++ test_grep ! "has type 100.*, expected 100.*" err &&
++ test_file_mode_staged 0755 change_notx_to_x &&
++ test_tick && git commit -m "redo: make change_notx_to_x executable" &&
++ test_file_mode_HEAD 0755 change_notx_to_x &&
++
++ git apply --index change_notx_to_x-0003-delete.patch &&
++ test_grep ! "has type 100.*, expected 100.*" err &&
++ test_file_mode_staged "" change_notx_to_x &&
++ test_tick && git commit -m "undo: remove change_notx_to_x" &&
++ test_file_mode_HEAD "" change_notx_to_x
++'
++
++test_expect_success 'git apply --reverse restores file modes (change_notx_to_x)' '
++ test_config core.fileMode false &&
++
++ git apply --index --reverse change_notx_to_x-0003-delete.patch &&
++ test_file_mode_staged 0755 change_notx_to_x &&
++ test_tick && git commit -m "undo: remove change_notx_to_x" &&
++ test_file_mode_HEAD 0755 change_notx_to_x &&
++
++ git apply --index --reverse change_notx_to_x-0002-chmod-0755.patch 2>err &&
++ test_grep ! "has type 100.*, expected 100.*" err &&
++ test_file_mode_staged 0644 change_notx_to_x &&
++ test_tick && git commit -m "undo: make change_notx_to_x executable" &&
++ test_file_mode_HEAD 0644 change_notx_to_x &&
++
++ git apply --index --reverse change_notx_to_x-0001-create-0644.patch 2>err &&
++ test_grep ! "has type 100.*, expected 100.*" err &&
++ test_file_mode_staged "" change_notx_to_x &&
++ test_tick && git commit -m "undo: add change_notx_to_x as not executable" &&
++ test_file_mode_HEAD "" change_notx_to_x
++'
++
test_expect_success POSIXPERM 'patch mode for new file is canonicalized' '
+ cat >patch <<-\EOF &&
+ diff --git a/non-canon b/non-canon
--
2.49.0
next prev parent reply other threads:[~2025-05-23 17:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 22:02 [PATCH] apply: set file mode when --reverse creates a deleted file Mark Mentovai
2025-05-22 22:24 ` Kristoffer Haugsbakk
2025-05-22 23:15 ` Junio C Hamano
2025-05-22 22:58 ` Junio C Hamano
2025-05-22 23:48 ` Mark Mentovai
2025-05-23 14:49 ` Junio C Hamano
2025-05-23 17:21 ` Mark Mentovai [this message]
2025-05-23 17:21 ` [PATCH v2 1/2] t4129: test that git apply warns for unexpected mode changes Mark Mentovai
2025-05-23 23:32 ` Junio C Hamano
2025-05-24 3:10 ` Mark Mentovai
2025-05-23 17:21 ` [PATCH v2 2/2] apply: set file mode when --reverse creates a deleted file Mark Mentovai
2025-05-23 23:44 ` Junio C Hamano
2025-05-24 3:19 ` Mark Mentovai
2025-05-24 3:40 ` [PATCH v3 0/2] " Mark Mentovai
2025-05-24 3:40 ` [PATCH v3 1/2] t4129: test that git apply warns for unexpected mode changes Mark Mentovai
2025-05-24 3:40 ` [PATCH v3 2/2] apply: set file mode when --reverse creates a deleted file Mark Mentovai
2025-05-27 13:56 ` [PATCH v3 0/2] " Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250523172154.93810-1-mark@chromium.org \
--to=mark@chromium.org \
--cc=chandrapratap3519@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johannes.schindelin@gmx.de \
--cc=kristofferhaugsbakk@fastmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).