1 files changed, 0 insertions, 82 deletions
diff --git a/doc/bugs/Weird_directories_appearing.mdwn b/doc/bugs/Weird_directories_appearing.mdwn
deleted file mode 100644
index ea85cead6..000000000
--- a/doc/bugs/Weird_directories_appearing.mdwn
+++ /dev/null
@@ -1,82 +0,0 @@
-Hello!
-
-Can someone explain this behavior to me? System is ArchLinux with the newest prebuilt tarballs as of Jan 12th.
-
-     ~ % mkdir GA1
-     ~ % cd GA1
-     ~/GA1 % git init      
-    Initialized empty Git repository in /home/florian/GA1/.git/
-     ~/GA1 (git)-[master] % git annex init
-    init  ok
-    (Recording state in git...)
-     ~/GA1 (git)-[master] % echo "GA1" > testfile
-     ~/GA1 (git)-[master] % git annex add .
-    add testfile ok
-    (Recording state in git...)
-     ~/GA1 (git)-[master] % git annex sync
-    commit  ok
-     ~/GA1 (git)-[master] % cd ..
-
-     ~ % git clone GA1 GA2
-    Cloning into 'GA2'...
-    done.
-     ~ % cd GA2
-     ~/GA2 (git)-[master] % git annex init
-    init  ok
-    (Recording state in git...)
-     ~/GA2 (git)-[master] % git annex get .
-    get testfile (merging origin/git-annex into git-annex...)
-    (Recording state in git...)
-    (from origin...) ok
-    (Recording state in git...)
-     ~/GA2 (git)-[master] % git annex unlock testfile 
-    unlock testfile (copying...) ok
-     ~/GA2 (git)-[master] % echo "GA2" > testfile 
-    commit  ok
-    pull origin 
-    ok
-    push origin 
-    Counting objects: 27, done.
-    Delta compression using up to 4 threads.
-    Compressing objects: 100% (16/16), done.
-    Writing objects: 100% (20/20), 1.88 KiB | 0 bytes/s, done.
-    Total 20 (delta 2), reused 0 (delta 0)
-    To /home/florian/GA1
-       f0654aa..8d0bdf9  master -> synced/master
-     * [new branch]      git-annex -> synced/git-annex
-    ok
-     ~/GA2 (git)-[master] % cd ../GA1
-
-     ~/GA1 (git)-[master] % git annex sync
-    (merging synced/git-annex into git-annex...)
-    commit  ok
-    merge synced/master 
-    Updating f0654aa..8d0bdf9
-    Fast-forward
-     e6a/e57/SHA256E-s4--241dca52164d30bee7a0be8c097f02e382acff765a9d4136718a37abd437a57c.log | 1 +
-     testfile                                                                                 | 2 +-
-     2 files changed, 2 insertions(+), 1 deletion(-)
-     create mode 100644 e6a/e57/SHA256E-s4--241dca52164d30bee7a0be8c097f02e382acff765a9d4136718a37abd437a57c.log
-    ok
-
-     ~/GA1 (git)-[master] % ll
-    total 4
-    drwxr-x--- 1 florian florian   6 Jan 12 13:59 e6a/
-    lrwxrwxrwx 1 florian florian 178 Jan 12 13:59 testfile -> .git/annex/objects/V6/ZM/SHA256E-s4--241dca52164d30bee7a0be8c097f02e382acff765a9d4136718a37abd437a57c/SHA256E-s4--241dca52164d30bee7a0be8c097f02e382acff765a9d4136718a37abd437a57c
-
-     ~/GA1 (git)-[master] % cat e6a/e57/SHA256E-s4--241dca52164d30bee7a0be8c097f02e382acff765a9d4136718a37abd437a57c.log
-    1389531554.951523s 1 dedf9799-0131-4773-8939-8f76294fa8e9
-
-Where does the e6a directory comes from? I don't suspect a bug there, but in my conception of git-annex.
-
-Thanks!
-Florian
-
-> [[fixed|done]]
-> 
-> I know someone reported this a looong time ago (years), and I cannot find
-> that bug report. Probably I closed it because I was unable to find a way
-> to reproduce it.
-> 
-> The spurious log files can be safely removed from your working tree.
-> --[[Joey]]