Added a comment
This commit is contained in:
parent
2f183e7b7c
commit
45740d66cd
1 changed files with 17 additions and 0 deletions
|
@ -0,0 +1,17 @@
|
||||||
|
[[!comment format=mdwn
|
||||||
|
username="beryllium@5bc3c32eb8156390f96e363e4ba38976567425ec"
|
||||||
|
avatar="http://cdn.libravatar.org/avatar/62b67d68e918b381e7e9dd6a96c16137"
|
||||||
|
subject="comment 3"
|
||||||
|
date="2023-01-05T07:16:30Z"
|
||||||
|
content="""
|
||||||
|
I should add, and this is not a commentary on the implementation of git-annex, etc... but having limited experience with BSD, and understanding that it uses different line endings for text files (???)... and other considerations... the git hooks mechanism is powerful, but seemingly presents challenges for interoperability.
|
||||||
|
|
||||||
|
Maybe the right approach is actually... as I did... let the end-user find their own workaround. It seems it's not really a git-annex fault after all.
|
||||||
|
|
||||||
|
I initially thought that git-annex should write the file out correctly... but it kind of is. It's writing it out for the local sensibilities.
|
||||||
|
|
||||||
|
In this particular case, it's my challenge to solve, not the tools... if you agree, I'd be content to have this closed with no action.
|
||||||
|
|
||||||
|
But I leave it to your better judgement.
|
||||||
|
|
||||||
|
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue