summaryrefslogtreecommitdiff
path: root/doc/bugs/__34__annex_sync__34___gets_confused_when_operating_in_a_symlink__39__ed_dire...
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2014-05-29 15:23:05 -0400
committerGravatar Joey Hess <joey@kitenet.net>2014-05-29 15:23:05 -0400
commit1f6cfecc972b121fa42ea80383183bbaccc2195a (patch)
tree0a450c4226f5e05c2a3597a9f520376de281fffe /doc/bugs/__34__annex_sync__34___gets_confused_when_operating_in_a_symlink__39__ed_directory.mdwn
parenta95fb731cd117f35a6e0fce90d9eb35d0941e26e (diff)
remove old closed bugs and todo items to speed up wiki updates and reduce size
Remove closed bugs and todos that were least edited before 2014. Command line used: for f in $(grep -l '\[\[done\]\]' *.mdwn); do if [ -z $(git log --since=2014 --pretty=oneline "$f") ]; then git rm $f; git rm -rf $(echo "$f" | sed 's/.mdwn$//'); fi; done
Diffstat (limited to 'doc/bugs/__34__annex_sync__34___gets_confused_when_operating_in_a_symlink__39__ed_directory.mdwn')
-rw-r--r--doc/bugs/__34__annex_sync__34___gets_confused_when_operating_in_a_symlink__39__ed_directory.mdwn27
1 files changed, 0 insertions, 27 deletions
diff --git a/doc/bugs/__34__annex_sync__34___gets_confused_when_operating_in_a_symlink__39__ed_directory.mdwn b/doc/bugs/__34__annex_sync__34___gets_confused_when_operating_in_a_symlink__39__ed_directory.mdwn
deleted file mode 100644
index bbe37a8d6..000000000
--- a/doc/bugs/__34__annex_sync__34___gets_confused_when_operating_in_a_symlink__39__ed_directory.mdwn
+++ /dev/null
@@ -1,27 +0,0 @@
-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
-
-
-> I tried to reproduce this, and it doesn't happen any longer. Tested in
-> both direct and indirect mode.
->
-> I think this bug was another manifestation of a bug that got fixed a
-> while ago where the direct mode repository updater got confused when run
-> in a subdirectory of the repository, and put files under that subdir that
-> were supposed to go under the root of the repository.
->
-> [[done]] --[[Joey]]