mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Added a comment

Browse source
This commit is contained in:
sb-beryllium@6e2c477eac63b823bd315ef8aaf5f93173c1f15b 2023-01-07 13:05:24 +00:00 • committed by admin
parent a5d3328a6f
commit 31f500bab6
1 changed files with 22 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
doc/bugs/CRLF_breaks_interoperability_Win-Ux__58__..post-receive/comment_4_82103077cde68c3b6a70dcf70c4ed837._comment Normal file
View file

@ -0,0 +1,22 @@
[[!comment format=mdwn
username="sb-beryllium@6e2c477eac63b823bd315ef8aaf5f93173c1f15b"
nickname="sb-beryllium"
avatar="http://cdn.libravatar.org/avatar/ef62105380b73ef91d760ec327c14e22"
subject="comment 4"
date="2023-01-07T13:05:23Z"
content="""
Apologies, this is beryllium (by alias)... due to unforeseen circumstances, I have had to register with a different email address. I am hoping this is a temporary situation.
Further apologies... I acknowledge that I am vacillating somewhat, but I've reverted to thinking that the hooks should be generated with unix line-endings (LF).
The reason I say this is, it does appear that the pseudo-standard for files under the .git directory is that they use unix line-endings only (perhaps an actual, documented standard... I'm not sure where to look/ask to confirm it).
This is the case for files such as .git/config, and .git/refs/** etc... under Git for Windows, and even JGit running with Windows native Java.
So to me.. it seems to make sense that hook files should have unix line-endings exclusively.
There are possible other mitigations... but that's where I stand with that finally. I'm still not fussed if no actions is determined to be the best course of action.
Thanks regardless.
"""]]