removed

diff --git a/doc/special_remotes/rsync/comment_3_06c44abf86dde69b504c9017f2c3114d._comment b/doc/special_remotes/rsync/comment_3_06c44abf86dde69b504c9017f2c3114d._comment
deleted file mode 100644 (file)
index 41395db..0000000
--- a/doc/special_remotes/rsync/comment_3_06c44abf86dde69b504c9017f2c3114d._comment
+++ /dev/null
@@ -1,19 +0,0 @@
-[[!comment format=txt
- username="diepes"
- ip="105.227.34.36"
- subject="comment 3"
- date="2013-03-29T22:03:38Z"
- content="""
- * It sound to me it would be 1st prize if the cloud provider supported the git-annex functionality over ssh. 
- * Then it could be a full git-annex repo, and used for recovery if my laptop with the git info gets lost.
-
- * From special remotes \"These can be used just like any normal remote by git-annex\" 
- * Your comment \"No, special remotes do not contain a copy of the git repository\"
-
- * so a special remote is 
-1. A. just a remote filesystem, that contains the objects with sha1 names ? 
-2. B. there is no git info and thus no file name & directory details or am i missing something ? 
-3. C. you can't use the remote as a cloud drive to sync changes e.g. file moves, renames between two other git-annex repositories ? (no meta data) 4. D. the data on the cloud/rsync storage can not be used directly it has to moved into a git-annex capable storage location.
-
- * Would it not be better to mount the remote storage over ssh(sshfs) and then use full git-annex on mounted directory ?
-"""]]