From e5804b5c48617c11677251cdc9ef74d6432e2496 Mon Sep 17 00:00:00 2001 From: jgoerzen Date: Tue, 14 Jun 2016 22:08:44 +0000 Subject: Added a comment: Experienced this --- .../comment_2_35f59adc30fe743221f29bbfecff639b._comment | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/bugs/Empty_folders_don__39__t_get_remove/comment_2_35f59adc30fe743221f29bbfecff639b._comment (limited to 'doc') diff --git a/doc/bugs/Empty_folders_don__39__t_get_remove/comment_2_35f59adc30fe743221f29bbfecff639b._comment b/doc/bugs/Empty_folders_don__39__t_get_remove/comment_2_35f59adc30fe743221f29bbfecff639b._comment new file mode 100644 index 000000000..e471d3366 --- /dev/null +++ b/doc/bugs/Empty_folders_don__39__t_get_remove/comment_2_35f59adc30fe743221f29bbfecff639b._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="jgoerzen" + subject="Experienced this" + date="2016-06-14T22:08:43Z" + content=""" +Hi, + +I experienced this just now. Have a git-annex assistant repo set up (so using direct mode). + +On one machine, I mv'd entire directories out of the git-annex repo. + +The other machine saw the files deleted, but the directories remained. + +On the machine on which I mv'd directories out, git-annex actually re-created some of them with symlinks to now-nonexistant hashes! I have no idea why it did that. +"""]] -- cgit v1.2.3