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

comment

Browse source
This commit is contained in:
Joey Hess 2023-01-16 15:07:46 -04:00
parent ec0107098d
commit 9be56daf07
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 23 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

23
doc/bugs/Paths_behind_relative_symlinks_in_repo_don__39__t_work/comment_2_c4e6ab98e88add01eefe545551b12929._comment Normal file
View file

@ -0,0 +1,23 @@
[[!comment format=mdwn
username="joey"
subject="""comment 2"""
date="2023-01-16T18:56:42Z"
content="""
git-annex actually has very similar behavior to git. Consider from your example:
joey@darkstar:~/tmp/xx/git-annex-link>git annex get link-to-level1/file
error: pathspec 'link-to-level1/file' did not match any file(s) known to git
Did you forget to 'git add'?
get: 1 failed
Compare to:
joey@darkstar:~/tmp/xx/git-annex-link>git rm link-to-level1/file
fatal: pathspec 'link-to-level1/file' did not match any files
If anything, it seems that the bug is in `git-annex info` for behaving
differently in this case when run on a file behind a symlink.
Also this is not a problem if you `cd` to the symlink and then run commands
operating on relative files.
"""]]