From 022c14ec026b763323a1b58e4f2b920985906185 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 28 Nov 2022 14:07:35 -0400 Subject: [PATCH] comment --- ..._1_a9501e2f347b957e7dc53a06fe59cff4._comment | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 doc/bugs/CRLF_breaks_interoperability_Win-Ux__58__..post-receive/comment_1_a9501e2f347b957e7dc53a06fe59cff4._comment diff --git a/doc/bugs/CRLF_breaks_interoperability_Win-Ux__58__..post-receive/comment_1_a9501e2f347b957e7dc53a06fe59cff4._comment b/doc/bugs/CRLF_breaks_interoperability_Win-Ux__58__..post-receive/comment_1_a9501e2f347b957e7dc53a06fe59cff4._comment new file mode 100644 index 0000000000..dadc7b49e4 --- /dev/null +++ b/doc/bugs/CRLF_breaks_interoperability_Win-Ux__58__..post-receive/comment_1_a9501e2f347b957e7dc53a06fe59cff4._comment @@ -0,0 +1,17 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2022-11-28T17:57:19Z" + content=""" +You can edit the hooks that git-annex installs however you need to. It will +not overwrite modified hook files. If you edit this hook to have unix line +endings, does the hook still work when using this repository on windows? + +Actually, I'm having difficulty seeing how the CR could have gotten into +that hook. `mkHookScript` uses `unlines` which behaves the same on Windows +as on Linux, so in either case lines should be separated only by `\n`. + +This makes me wonder if something else modified the hook after git-annex +wrote it. If so, `git-annex init` should complain that the hook is +modified. +"""]]