Added a comment: Rationale behind deleting and readding the symlinks on a move or rename
This commit is contained in:
parent
aab3a552f9
commit
c550663512
1 changed files with 13 additions and 0 deletions
|
@ -0,0 +1,13 @@
|
|||
[[!comment format=mdwn
|
||||
username="cardoso-neto"
|
||||
avatar="http://cdn.libravatar.org/avatar/d90a656df072f3a29da54302c190c696"
|
||||
subject="Rationale behind deleting and readding the symlinks on a move or rename"
|
||||
date="2020-08-20T18:36:47Z"
|
||||
content="""
|
||||
I couldn't find an explanation for this using the search bar, so I thought this would be as good a place as any to ask this.
|
||||
|
||||
Even when I run `git mv` on git annexed file, git annex always changes it for what looks like a combo of `git rm old_symlink; git add new_symlink`
|
||||
|
||||
I guess it does this when that pre-commit hook you mentioned runs.
|
||||
Why?
|
||||
"""]]
|
Loading…
Reference in a new issue