blob: 96d1d4d2ee877c185ba9aabe41e4a28bcbd7564b (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
|
What steps will reproduce the problem?
* Create a symlink to a directory in your annex repository, like e.g. ~/Notes -> ~/annex/Notes
* cd into ~/Notes
* execute 'git annex sync <remote>', assuming that <remote> has made some changes
What is the expected output? What do you see instead?
If <remote> has made a change to, say, ~/annex/Documents/test.txt, the sync unexpectedly creates the new test.txt at ~/Notes/Documents/test.txt.
It should either magically figure out that it has to create the file relative to the repository's root (i.e. ~/annex) or throw an error instead.
What version of git-annex are you using? On what operating system?
git-annex version: 4.20130323
OS: Archlinux
Shell: zsh
|
