File: Automatic_fallback_to_special_remote_with_sameas.mdwn

package info (click to toggle)
git-annex 10.20250416-2
  • links: PTS, VCS
  • area: main
  • in suites: trixie
  • size: 73,572 kB
  • sloc: haskell: 90,656; javascript: 9,103; sh: 1,469; makefile: 211; perl: 137; ansic: 44
file content (7 lines) | stat: -rw-r--r-- 712 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
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 already when specifying sameas, but apparently it isn't. Is it possible to achieve this?