From bbdfe6b910a443833c821ae1ec1a26a14768930a Mon Sep 17 00:00:00 2001 From: "m.risse@77eac2c22d673d5f10305c0bade738ad74055f92" Date: Tue, 25 Jun 2024 15:59:36 +0000 Subject: [PATCH] --- doc/forum/Automatic_fallback_to_special_remote_with_sameas.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/forum/Automatic_fallback_to_special_remote_with_sameas.mdwn b/doc/forum/Automatic_fallback_to_special_remote_with_sameas.mdwn index 78abfc0ef1..d58e515afd 100644 --- a/doc/forum/Automatic_fallback_to_special_remote_with_sameas.mdwn +++ b/doc/forum/Automatic_fallback_to_special_remote_with_sameas.mdwn @@ -4,4 +4,4 @@ I've implemented a special remote that is able to do store and remove operations 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? +I expected this to be the case already when specifying sameas, but apparently it isn't. Is it possible to achieve this?