diff options
| author |  diepes <diepes@web> | 2013-03-29 22:01:17 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2013-03-29 22:01:17 +0000 |
| commit | 6507182bde2fa89f6cfd7d8d4b6733494c1c6637 (patch) | |
| tree | a0f4cd954cdc97088dc44252bb32edb2afbf4bcf | |
| parent | babf9822dd7326e7d96eee4fc1057d64c38e4561 (diff) | |
removed
| -rw-r--r-- | doc/special_remotes/rsync/comment_3_7235b9201cb486e1ebdd3fcbb2833355._comment | 24 |
1 files changed, 0 insertions, 24 deletions
diff --git a/doc/special_remotes/rsync/comment_3_7235b9201cb486e1ebdd3fcbb2833355._comment b/doc/special_remotes/rsync/comment_3_7235b9201cb486e1ebdd3fcbb2833355._comment deleted file mode 100644 index e4f90a169..000000000 --- a/doc/special_remotes/rsync/comment_3_7235b9201cb486e1ebdd3fcbb2833355._comment +++ /dev/null @@ -1,24 +0,0 @@ -[[!comment format=mdwn - username="diepes" - ip="105.227.34.36" - subject="Rather use sshfs ? and No sync to 2nd repo ?" - date="2013-03-29T22:00:16Z" - 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 -A. just a remote filesystem, that contains the objects with sha1 names ? -B. there is no git info and thus no file name & directory details or am i missing something ? -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) -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 ? - - - - -"""]] |