From 65f5a0f228b4d13455539016a544bce36aa91eeb Mon Sep 17 00:00:00 2001 From: "m.risse@77eac2c22d673d5f10305c0bade738ad74055f92" Date: Tue, 25 Jun 2024 10:46:13 +0000 Subject: [PATCH] --- .../Automatic_fallback_to_special_remote_with_sameas.mdwn | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 doc/forum/Automatic_fallback_to_special_remote_with_sameas.mdwn diff --git a/doc/forum/Automatic_fallback_to_special_remote_with_sameas.mdwn b/doc/forum/Automatic_fallback_to_special_remote_with_sameas.mdwn new file mode 100644 index 0000000000..78abfc0ef1 --- /dev/null +++ b/doc/forum/Automatic_fallback_to_special_remote_with_sameas.mdwn @@ -0,0 +1,7 @@ +I have a normal git/git-annex remote configured via https called "origin". This means for git-annex purposes (copy/move/drop/etc.) it is read-only. + +I've implemented a special remote that is able to do store and remove operations on that same location, also via https. I configured this special remote with `--sameas=origin`, to signify that relationship. + +Now ideally I would like operations like `git annex drop --from=origin` or `git annex copy --to=origin` to notice that origin itself cannot be used for these, and instead automatically fallback to the special remote that can do them. + +I expected this to be the case when already specifying sameas, but apparently it isn't. Is it possible to achieve this?