diff options
| author |  http://a-or-b.myopenid.com/ <http://a-or-b.myopenid.com/@web> | 2013-02-13 05:12:41 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2013-02-13 05:12:41 +0000 |
| commit | 5431cdfaa23be70abbe8a7f8c58790b8763c1e49 (patch) | |
| tree | 17aee4682c565eab3aaf3dd88ad1ba75f80a6786 /doc | |
| parent | 8d4559918d822e61ff724489d8928e4b44dda913 (diff) | |
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/forum/Different_annexes_pointing_to_same_special_remote__63__.mdwn | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/forum/Different_annexes_pointing_to_same_special_remote__63__.mdwn b/doc/forum/Different_annexes_pointing_to_same_special_remote__63__.mdwn new file mode 100644 index 000000000..8413a6e08 --- /dev/null +++ b/doc/forum/Different_annexes_pointing_to_same_special_remote__63__.mdwn @@ -0,0 +1,6 @@ +Is there likely to be any problem in pointing different annexes to the same special remote (i.e. rsync/box.com/etc.) ? + +As the objects are stored based on their SHA256 key the expectation is that the chance of collision is is small. + +The only problem I can foresee is where the same content is stored in more than one annex and it is deleted in the remote in one annex, but not the other - there won't be any protection against that, but for non-overlapping content this risk should be negligible. + |