diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2017-06-07 13:41:04 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2017-06-07 13:45:18 -0400 |
| commit | 656efe58861dc621c462eaee6fe795395c0d343c (patch) | |
| tree | 18b802adf3048e11567ec785893929600c394e76 /doc | |
| parent | de780348c8f92be1a9a6f18a708ba3e730ac7149 (diff) | |
analysis
Also, added a comment to Assistant/Threads/Merger.hs to explain
why it only merges from /synced/ branches.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/bugs/bare_remote_is_not_automatically_synced_to_local_repo/comment_5_aeea3ff59c8493c87c313fbaf7614f20._comment | 36 |
1 files changed, 36 insertions, 0 deletions
diff --git a/doc/bugs/bare_remote_is_not_automatically_synced_to_local_repo/comment_5_aeea3ff59c8493c87c313fbaf7614f20._comment b/doc/bugs/bare_remote_is_not_automatically_synced_to_local_repo/comment_5_aeea3ff59c8493c87c313fbaf7614f20._comment new file mode 100644 index 000000000..92241bf51 --- /dev/null +++ b/doc/bugs/bare_remote_is_not_automatically_synced_to_local_repo/comment_5_aeea3ff59c8493c87c313fbaf7614f20._comment @@ -0,0 +1,36 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 5""" + date="2017-06-07T16:40:18Z" + content=""" +This has nothing to do with repository groups; it's the git branch +not getting synced by the assistant when master is updated in the +bare repository. + +This is easy enough to repoduce. + +The assistant relies on `git annex remotedaemon` to notice changes in +remotes, and the remotedaemon only supports remotes accessed via ssh, not +on a local drive. + +The assistant has some special case handling for repositories on +removable drives, which lets those be plugged in and syncs with them. +Removable drives are also why the remotedaemon does not watch repositories +on a local drive. If the drive is removable, the remotedaemon would +keep it always busy, by having directories open for inotify, +and so prevent a clean removal of the drive. + +So, I don't think anything can be done about this, at least in the default +configuration. One workaround it using a ssh url for the remote will +make the remotedaemon watch it for changes. + +I could add a non-default configuration setting that +makes a remote on a local drive be watched for changes. + +But, it's not clear to me why you'd want to have the changes be pushed +in to a repository on a removable drive, rather than pushing/syncing +with the repository where the assistant is running. The assistant would +then sync changes it received on to the removable drive. That seems like a +better setup, will still work when the drive is removed for a while, +and is already supported. +"""]] |