From c5f86397cd899edf490ce262ab0bdbc5d432a13d Mon Sep 17 00:00:00 2001 From: Atemu Date: Wed, 22 Jun 2022 12:24:22 +0000 Subject: [PATCH] Added a comment --- ..._38d7c0531d68803b1d7910c598aab38c._comment | 35 +++++++++++++++++++ 1 file changed, 35 insertions(+) create mode 100644 doc/forum/How_to_make_this_workflow_possible__63__/comment_1_38d7c0531d68803b1d7910c598aab38c._comment diff --git a/doc/forum/How_to_make_this_workflow_possible__63__/comment_1_38d7c0531d68803b1d7910c598aab38c._comment b/doc/forum/How_to_make_this_workflow_possible__63__/comment_1_38d7c0531d68803b1d7910c598aab38c._comment new file mode 100644 index 0000000000..1b0cf01f60 --- /dev/null +++ b/doc/forum/How_to_make_this_workflow_possible__63__/comment_1_38d7c0531d68803b1d7910c598aab38c._comment @@ -0,0 +1,35 @@ +[[!comment format=mdwn + username="Atemu" + avatar="http://cdn.libravatar.org/avatar/d1f0f4275931c552403f4c6707bead7a" + subject="comment 1" + date="2022-06-22T12:24:21Z" + content=""" +> The one caveat here is `git annex sync --content --no-pull` seems to ignore the no-pull option and tries to redownload all the raw files back to the laptop. How to do a one-way sync (laptop -> remote only with content)? + +AFAICT, pull only concerns `git` actions, not `git-annex` actions like transferring content. + +What your laptop's repo tries to copy depends on what content it wants and numcopies. + +The latter probably isn't your problem since you should have at least 2 copies of everything distributed over the drives. +The former should ideally be solved with a proper customised groups setup but you can also set a wanted expression or use the built-in groups which is probably your best option. Your laptop's repo should be set to `client` or `manual`. + +See https://git-annex.branchable.com/git-annex-preferred-content/ and https://git-annex.branchable.com/preferred_content/standard_groups/ + +> XMP sidecars that are produced are tracked in regular git + +Have you set `annex.largefiles` to anything? + +Sidecar files are just XML AFAICT, so a filter that would only add files with binary mimeencoding to annex would exclude these and add them to regular git. + +If you haven't touched that setting (double check with `git config`), that's a bug. + +> Try to sync with any available remote (this is the part I can't seem to figure out. I wish git-annex could be detect and try to to push to all available remotes instead me having to track which remotes are available). +> `git annex [copy|move]` have the `--to=here` option which will copy/move files from remotes to local repo. It would be exceptionally useful to have a `--to=reachable` option to send files to any reachable remote instead of having to copy/moves to each remote individually. + +By default, sync syncs with *all* available remotes. + +How exactly are your repo's remotes set up? + +What does it to when syncing that you don't want it to? + +"""]] -- 2.30.2