From 05add2e19da3b79937de24e727aa93e5d136179d Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 23 Apr 2020 16:21:11 -0400 Subject: [PATCH] add comment --- ..._47b3095cd203477cc3e607d9cf840823._comment | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 doc/bugs/git_annex_sync__58___--fast_and_REMOTE_should_be_exclusive/comment_1_47b3095cd203477cc3e607d9cf840823._comment diff --git a/doc/bugs/git_annex_sync__58___--fast_and_REMOTE_should_be_exclusive/comment_1_47b3095cd203477cc3e607d9cf840823._comment b/doc/bugs/git_annex_sync__58___--fast_and_REMOTE_should_be_exclusive/comment_1_47b3095cd203477cc3e607d9cf840823._comment new file mode 100644 index 0000000000..3b10626510 --- /dev/null +++ b/doc/bugs/git_annex_sync__58___--fast_and_REMOTE_should_be_exclusive/comment_1_47b3095cd203477cc3e607d9cf840823._comment @@ -0,0 +1,22 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2020-04-23T19:29:59Z" + content=""" +--fast is a global option that is parsed for all commands and +does varying different things in different commands. +That's mostly a relic from before git-annex's option parser supported +per-command options. It would be hard to untangle at this point. + +What it actually does currently is sync with the remotes you listed and +then the --fast *adds* whatever fastest remote it can find. That must +explain the behavior you saw, although I would expect that it would have +first synced with the remote you listed and only after that, +started filling the fast remote. + +Anyway, it seems that `git annex sync --fast foo bar` +should either pick whichever of foo or bar currently has the lowest cost, +and sync with it, or it should error out as you suggest (necessarily after +option parsing). Adding another remote that has a low cost is certianly too +surprising. +"""]]