From 52c0fc97e3b9b192089c4b6d8606d5a4de325426 Mon Sep 17 00:00:00 2001 From: nobodyinperson Date: Mon, 1 May 2023 08:50:10 +0000 Subject: [PATCH] Added a comment: git-annex relaying syncs across remotes --- .../comment_3_9b6ecb7342aab7f0320ed7567ee5fa0b._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/git_annex_sync_update_remote/comment_3_9b6ecb7342aab7f0320ed7567ee5fa0b._comment diff --git a/doc/forum/git_annex_sync_update_remote/comment_3_9b6ecb7342aab7f0320ed7567ee5fa0b._comment b/doc/forum/git_annex_sync_update_remote/comment_3_9b6ecb7342aab7f0320ed7567ee5fa0b._comment new file mode 100644 index 0000000000..1442363be6 --- /dev/null +++ b/doc/forum/git_annex_sync_update_remote/comment_3_9b6ecb7342aab7f0320ed7567ee5fa0b._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="nobodyinperson" + avatar="http://cdn.libravatar.org/avatar/736a41cd4988ede057bae805d000f4f5" + subject="git-annex relaying syncs across remotes" + date="2023-05-01T08:50:10Z" + content=""" +It does update the state of all available remotes of the `my_system` you're executing git-annex from. I would also love to see git-annex propagate the changes across the graph of connected remotes as far as it gets. It already has permissions to run git-annex on the remote server, so it could trigger a `git annex sync` from there, then reaching out for all configured remotes it has configured itself. But I'm sure @joey has a good reason not to do this, it screams of potential race conditions and git locking weirdness. But I don't know 🤷 +"""]] -- 2.30.2