mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Added a comment: backends vs special remotes

Browse source
This commit is contained in:
Ilya_Shlyakhter 2020-02-20 19:23:07 +00:00 committed by admin
parent 48fc8b7c4e
commit d521220e0e
1 changed files with 10 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
doc/backends/comment_31_32df8ec41dd8a6516b88b1871c998eb9._comment Normal file
View file

@ -0,0 +1,10 @@
[[!comment format=mdwn
username="Ilya_Shlyakhter"
avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
subject="backends vs special remotes"
date="2020-02-20T19:23:04Z"
content="""
@annex2384 \"Backend which doesn't store files at all?\" -- are you sure you're thinking of backends and not of [[special_remotes]]? Backends don't \"store files\", special remotes do. Backends create keys identifying specific contents.
Not sure I fully understand your use case, but you could write an [[external special remote|special_remotes/external]] that, for a given git-annex key, stores \"the location of possible local copies of the file\" -- e.g. using `SETSTATE` or `SETURIPRESENT`.
"""]]