diff options
author | Joey Hess <joey@kitenet.net> | 2012-08-22 15:47:08 -0400 |
---|---|---|
committer | Joey Hess <joey@kitenet.net> | 2012-08-22 15:47:08 -0400 |
commit | dfb67090644af0024abcefe885744df9a46d094d (patch) | |
tree | 55392cdae476aa436c46fc5e95b6230a62ca028c /doc | |
parent | e43feeb5b439d3cc8078b52a18a5a8568ceee2ae (diff) |
blog for the day
Diffstat (limited to 'doc')
-rw-r--r-- | doc/design/assistant/blog/day_62__smarter_syncing.mdwn | 21 |
1 files changed, 21 insertions, 0 deletions
diff --git a/doc/design/assistant/blog/day_62__smarter_syncing.mdwn b/doc/design/assistant/blog/day_62__smarter_syncing.mdwn new file mode 100644 index 000000000..28fa892d3 --- /dev/null +++ b/doc/design/assistant/blog/day_62__smarter_syncing.mdwn @@ -0,0 +1,21 @@ +Woke up this morning with most of the design for a smarter approach to +[[syncing]] in my head. (This is why I sometimes slip up and tell people I +work on this project 12 hours a day..) + +To keep the current `assistant` branch working while I make changes +that break use cases that are working, I've started +developing in a new branch, `assistant-wip`. + +In it, I've started getting rid of unnecessary expensive transfer scans. + +First optimisation I've done is to detect when a remote that was +disconnected has diverged its `git-annex` branch from the local branch. +Only when that's the case does a new transfer scan need to be done, to find +out what new stuff might be available on that remote, to have caused the +change to its branch, while it was disconnected. + +That broke a lot of stuff. I have a plan to fix it written down in +[[syncing]]. It'll involve keeping track of whether a transfer scan has +ever been done (if not, one should be run), and recording logs when +transfers failed, so those failed transfers can be retried when the +remote gets reconnected. |