Added a comment
This commit is contained in:
parent
b9f4009986
commit
513da0f1ef
1 changed files with 12 additions and 0 deletions
|
@ -0,0 +1,12 @@
|
|||
[[!comment format=mdwn
|
||||
username="http://joey.kitenet.net/"
|
||||
nickname="joey"
|
||||
subject="comment 3"
|
||||
date="2011-02-02T00:46:00Z"
|
||||
content="""
|
||||
Sorry for all the followups, but I see now that if you unannex, then add the file to git normally, and commit, the hook *does* misbehave.
|
||||
|
||||
This seems to be a bug. git-annex's hook thinks that you have used git annex unlock (or \"git annex edit\") on the file and are now committing a changed version, and the right thing to do there is to add the new content to the annex and update the symlink accordingly. I'll track this bug over at [[bugs/unannex_vs_unlock_hook_confusion]].
|
||||
|
||||
So, committing after unannex, and before checking the file into git in the usual way, is a workaround.
|
||||
"""]]
|
Loading…
Reference in a new issue