While I was looking at the differences between next..seen to catch
new topics that try to sneak style violations into the codebase, I
found this one (there was another in the same series).
----- >8 --------- >8 --------- >8 --------- >8 --------- >8 -----
Subject: [PATCH] fixup! t7527: create test for fsmonitor--daemon
Fix style violation of a shell-function definition
Signed-off-by: Junio C Hamano <gitster@xxxxxxxxx>
---
t/t7527-builtin-fsmonitor.sh | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/t/t7527-builtin-fsmonitor.sh b/t/t7527-builtin-fsmonitor.sh
index e62ec9aa3c..313c4fad34 100755
--- a/t/t7527-builtin-fsmonitor.sh
+++ b/t/t7527-builtin-fsmonitor.sh
@@ -213,43 +213,43 @@ test_expect_success 'status implicitly starts daemon' '
test_subcommand git fsmonitor--daemon start <.git/trace_implicit_2
'
-edit_files() {
+edit_files () {
echo 1 >modified
echo 2 >dir1/modified
echo 3 >dir2/modified
>dir1/untracked
}
-delete_files() {
+delete_files () {
rm -f delete
rm -f dir1/delete
rm -f dir2/delete
}
-create_files() {
+create_files () {
echo 1 >new
echo 2 >dir1/new
echo 3 >dir2/new
}
-rename_files() {
+rename_files () {
mv rename renamed
mv dir1/rename dir1/renamed
mv dir2/rename dir2/renamed
}
-file_to_directory() {
+file_to_directory () {
rm -f delete
mkdir delete
echo 1 >delete/new
}
-directory_to_file() {
+directory_to_file () {
rm -rf dir1
echo 1 >dir1
}
-verify_status() {
+verify_status () {
git status >actual &&
GIT_INDEX_FILE=.git/fresh-index git read-tree master &&
GIT_INDEX_FILE=.git/fresh-index git -c core.useBuiltinFSMonitor= status >expect &&
--
2.34.1-568-g69e9fd72b5
