aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2016-09-07 11:11:54 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2016-09-07 11:11:54 -0400
commiteee91ebceeb9057c86b72fb80e329dc53743ccb3 (patch)
treec9d786b46eece708437f8f2a2002eb716f2a49d4
parent1c9d748e89415d183ebe86c6edc771d42c501cf9 (diff)
followup
-rw-r--r--doc/todo/Specify_maximum_usable_space_per_remote/comment_3_afc7f278c02d7bf9f92a90e51cb5a2a9._comment19
1 files changed, 19 insertions, 0 deletions
diff --git a/doc/todo/Specify_maximum_usable_space_per_remote/comment_3_afc7f278c02d7bf9f92a90e51cb5a2a9._comment b/doc/todo/Specify_maximum_usable_space_per_remote/comment_3_afc7f278c02d7bf9f92a90e51cb5a2a9._comment
new file mode 100644
index 000000000..02ad7ca40
--- /dev/null
+++ b/doc/todo/Specify_maximum_usable_space_per_remote/comment_3_afc7f278c02d7bf9f92a90e51cb5a2a9._comment
@@ -0,0 +1,19 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 3"""
+ date="2016-09-07T15:08:37Z"
+ content="""
+git-annex repositories can all be clones of one another, but not currently
+connected. They can stay disconnected for an arbitrary amount of time,
+up to forever.
+
+For example, /media/usb/annex can be packed up, sent half way around the
+world and used with a different computer, which has no way to communicate
+with its parent ~/annex on the original computer.
+
+So, git-annex has to deal with split-brain and other distributed
+inconsistencies. And it does. However, a keeping count of how much space is
+used on a remote can't be consistent in these kinds of situations, unless,
+as I said, the count is kept in sync using the remote in question, and not
+information in the git-annex repositories.
+"""]]