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

comment

Browse source
This commit is contained in:
Joey Hess 2017-04-07 16:25:38 -04:00
commit 1e4bee253c
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 23 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

23
doc/bugs/annex_doesn__39__t_fixup_symlinks_when___34__git_commit_path__95__to__95__repo__34___is_used/comment_1_b90f22ce0ab931658856e949ac227985._comment Normal file
View file

@ -0,0 +1,23 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2017-04-07T20:16:45Z"
content="""
There's nothing special about using the absolute path; "git commit ."
or "git commit thefile" will behave the same.
This is the git false index problem. Since git commit in these situations
runs the pre-commit hook with a false index file, changes made to that
index file won't be visible after the commit.
So, if `git annex pre-commit` fixes symlinks in this situation,
the right thing will be committed, but then the old index will have the old
symlinks staged, which will result in `git status` after the commit showing
modification to the files you just staged and committed!
Short of having a post-commit hook come along and fix up the index to match
what was committed, I don't see anything git-annex can do better. Well, it
could prevent such commits even being made, I suppose, or warn.
It's a pity git uses this false index file in this situation.
"""]]